Learn how to coordinate several Scrum Teams building one product without drowning in dependencies, duplication and disconnected ceremonies. Master the core scaling patterns — a single Product Backlog, cross-team coordination and a shared Sprint Review — and know when you are scaling a product versus managing a portfolio.
Watch the free preview
Why scaling Scrum is a coordination problem, not a Scrum problem — free to watch, no account needed.
What you'll learn
- Explain why coordination, not team-level Scrum, is the hard problem when scaling
- Distinguish scaled Scrum (one product, many teams) from portfolio management (many products, many teams)
- Apply core scaling patterns — a single Product Backlog, Scrum of Scrums and a shared Sprint Review
- Diagnose disconnected multi-team delivery and design a shared coordination mechanism
- Produce a Multi-Team Coordination Design Template for a real product
Syllabus
The Scaling Problem and What It Really Is
Why scaling Scrum is a coordination problem, not a Scrum problemFree preview
One product, many teams versus many products, many teams
Cross-Team Coordination Techniques
The core coordination patterns — shared backlog, Scrum of Scrums, shared review
Integration and the single Definition of Done
Applying Scaling to Real IT Work
Managing dependencies and shared components across teams
Case study — three teams, three disconnected Sprint Reviews
Making Scaling Stick
Building your Multi-Team Coordination Design Template
Common traps and scaling anti-patterns