Complex Projects
Complex Projects tests whether you can scale Scrum without destroying its feedback loops. EXIN Agile Scrum questions often describe multiple teams, dependencies, distributed sites, or fixed-scope contracts, and ask what the Product Owner should change.
Why complexity changes the game
- More teams create dependencies, integration risk, and communication paths. Adding people increases coordination cost.
- Keep teams small, stable, and cross-functional, and align them to a product rather than a component where possible.
- A shared product vision and a single ordered product backlog keep priority coherent. At scale, a chief Product Owner can hold overall accountability while area Product Owners handle sections.
Coordination mechanisms
- Team of teams: a Scrum of Scrums of ambassadors coordinates cross-team impediments, dependencies, and integration. It is not a management status layer.
- Synchronize Sprint cadence and share a common definition of done so increments integrate.
- Make dependencies visible in refinement: mark them, order them, and test integration continuously.
- Use a lightweight intentional architecture and design guidelines to prevent chaos while allowing emergent design inside teams.
- Distributed teams need overlapping hours, explicit working agreements, and written decisions; do not rely on hallway conversation.
Contracts and governance
- Fixed-price, fixed-scope contracts fight empirical delivery. Prefer fixed time and cost with a prioritized backlog and variable scope.
- Governance should inspect outcomes and risks, not demand detailed upfront specifications.
Worked example
Four teams build one product. Each has its own Product Owner and backlog, and integration fails at the end. Better design: one chief Product Owner accountable for the overall product backlog, area Product Owners for sections, a shared definition of done that includes integration tests, a Scrum of Scrums for dependency resolution, and one synchronized Sprint cadence. Reasoning: local optimization creates global delays; shared ordering and continuous integration expose problems while they are still cheap to fix.
Traps that cost marks
- Scaling means one big team: large groups lose the benefits of small self-organizing units.
- Each team can have its own definition of done at scale: that hides integration debt.
- The Scrum of Scrums is a management status meeting: it exists for coordination and impediment removal.
- A chief Product Owner makes all team-level decisions: delegate detailed ordering, keep overall accountability.
- More documentation solves distributed coordination: working agreements and integration do more.