Learn how the three Scrum accountabilities behave when one product spans many teams, and why a single Product Owner or integration team can quietly become a bottleneck. You will scale accountability without diluting it, using Nexus, SAFe and LeSS as reference points, and build a Scaled Accountability Map for your own context.
Watch the free preview
Why a single accountability becomes a bottleneck at scale — free to watch, no account needed.
What you'll learn
- Explain the three Scrum accountabilities and what "accountable" means in the 2020 Scrum Guide
- Describe why a single Product Owner accountability becomes a bottleneck across many teams
- Distinguish scaling that distributes the work from scaling that wrongly distributes the accountability
- Compare how Nexus, SAFe and LeSS scale accountability without losing coherence
- Produce a Scaled Accountability Map that relieves bottlenecks while keeping a single voice of value
Syllabus
Why Scaling Breaks the Accountabilities
Why a single accountability becomes a bottleneck at scaleFree preview
The three accountabilities and what "accountable" really means
Scaling Without Diluting
Scaling the Product Owner accountability
The scaled-accountability mapping technique
Applying It to Real IT Work
Nexus in practice — the integration accountability
Case study — one Product Owner, five teams, one bottleneck
Making It Stick
Build your Scaled Accountability Map
Common traps and anti-patterns at scale