Implementing commercial off-the-shelf (COTS) software in a large organization comes with unique challengesāespecially when the tool is designed for just one environment and downtime disrupts daily operations. Discover how one team leveraged Scrum to overcome these obstacles and achieve rapid, reliable results with Oracle Primavera Unifier.
Oracle acquired Primavera Unifier as part of its expansion into the construction management space, aiming to provide highly configurable solutions for complex real estate and infrastructure projects.
Unifier, purchased by Oracle to enhance its construction management offerings, was only capable of operating in a single environmentāProductionāat the outset. Updates could render the tool unavailable for users, sometimes daily, creating friction and frustration. The organization anticipated these challenges and decided to apply Scrum practices to successfully implement and roll out the Unifier platform for real estate leasing across regions and languages.
What potential risks do you see when software updates take a critical system offline for users?
- Cross-Functional Scrum Team Formation: A dedicated team was assembled, led by a product owner for the real estate leasing module. Developers, tool configurators, process designers, testers, translators (for English, Spanish, and Portuguese), and training builders joined forces. The Scrum Master ensured the environment supported the team’s success, while stakeholders from regional and headquarters groups provided critical input.
- Roadmap and Multi-Environment Strategy: The team began by defining a clear product goal and a capabilities roadmap. Recognizing the need for flexibility, they established three separate product environments: Development, Test, and Production. This allowed safe iteration and validation without disrupting end users.
- Definition of Done: The team specified exactly when a workflow was “done,” starting with the user workflow, updating the security role matrix, building and testing in Development, then rebuilding and validating in Test. They documented every step, ensuring anyone could replicate the process in another environment. Once a product increment met the “done” criteria, it was rebuilt in Production and released to users feature by feature.
A shared agreement on the exact criteria that a product increment must meet to be considered complete and ready for release.
In global rollouts, including translators and training specialists in the Scrum team ensures every user group has access to the right features and support in their language from day one.
TABLE 12-1 Sample COTS Sprint & Release Definition of Done
Sprint |
Release |
|---|---|
Test environment |
Help desk review |
Configuration complete (workflow, roles, and so on) |
RFC approval |
Test cases updated |
Validate Production |
Security matrix updated |
Remove test records in Production |
ATF (automated testing framework) updated & passed |
Refresh Test environment |
Peer review |
Refresh Dev environment |
Security review |
|
Validate production ready |
|
Workflow documentation updated |
|
Data migration file updated |
|
RFC (request for change) submitted |
|
Update training materials |
|
Update Knowledge Base articles |
|
Release notes |
Why is it important to establish a clear and shared definition of “done” for every product increment?
The time interval between identifying a requirement and making it available for users in the production environment.
The team’s Scrum-based approach drove continuous progressāa releasable product increment was rebuilt in Production and delivered to users as soon as it met the team’s “done” criteria. Over time, functionality grew, and the implementation team became more efficient. But a breakthrough came during a retrospective: discovering a tool that could record every keystroke and mouse movement used to build workflows. By automating workflow creation and testing across environments, cycle time dropped significantly, and product quality soared. The improvement energized the team and highlighted the power of combining process discipline with technical innovation.
Automating repetitive configuration and testing steps can be a game-changer in large enterprise software implementations, freeing up teams for higher-value problem-solving and reducing errors.
How did the introduction of automation impact the team’s workflow and delivery speed?
Want to go deeper? The science behind reducing cycle time in Scrum teams
Reducing cycle time increases organizational agility and responsiveness: shorter cycles allow teams to deliver value more frequently, respond to changing requirements, and identify defects earlier. This aligns with Lean principles and is a direct measure of how quickly a team can turn an idea into working software for users. Tools that automate manual tasks further amplify these benefits by minimizing human error and freeing teams to focus on innovation and customer feedback.
Scrum is only effective for developing custom software from scratch and doesn’t fit commercial off-the-shelf (COTS) solutions.
Scrum can dramatically improve the implementation, configuration, and rollout of COTS products like Oracle Primavera Unifier, especially when teams adapt its practices to the constraints of the platform.
This particular retrospective took the team into high gear.
What was the key breakthrough that significantly reduced cycle time for the Unifier implementation team?
- Scrum teams can tackle even complex COTS implementations with the right environment and process design.
- Clear definitions of “done” and automated workflows lead to faster, higher-quality releases.
Practice creating a Definition of Done for a workflow or feature you might implement in your own organization.
- Select a simple feature or workflow you are familiar with.
- List the key steps, validations, and documentation updates required before it would be truly “done” and ready for release.
- Reflect on how your Definition of Done ensures quality and reduces ambiguity.
Think about a time you introduced automation or a new process to your team. How did it change the way you worked, and what lessons would you apply to a Scrum-based implementation like Unifier?
What is the main benefit of automating workflow configuration and testing in COTS implementations?
Tap to revealIt significantly reduces cycle time and improves product quality by minimizing manual errors and repetitive work.
Why was it important to have translators on the Unifier Scrum team?
Tap to revealBecause the product was released in English, Spanish, and Portuguese, ensuring all user groups could access and understand the new features.
What are the three environments established for Unifier implementation?
Tap to revealDevelopment, Test, and Production environments.
What is the definition of “cycle time” in the context of Scrum and product development?
Tap to revealThe time from identifying a requirement to making it available for users in the production environment.
Scrum can unlock rapid, high-quality delivery of even complex enterprise tools like Oracle Primavera Unifier when teams establish clear definitions of done, embrace automation, and adapt processes to technical constraints.
Automating repetitive configuration and testing steps dramatically reduces cycle time, boosts product quality, and empowers cross-functional teams to focus on value creation.
How might you apply the lessons from the Unifier implementation to your own team’s approach to software rollouts?
The Shift
- Scrum practices can be tailored to fit and improve even off-the-shelf enterprise tools, ensuring robust and flexible releases.
- Clear definitions of done and automation are critical for reducing cycle time and increasing delivery quality.
- Bringing together diverse rolesādevelopers, testers, translators, and trainersāfosters success in global software implementations.