Two Dimensions Of Agile At Scale
summary
Distinguishes two concrete problems: scaling breadth to change culture and shared services, and scaling depth to coordinate multiple teams on one product. Recommends building a protected “studio” with CI, API management, test automation and quick shared services so teams don’t wait 20 business days / 60 business days for tickets or environments. Uses Nexus patterns — group sprint planning, a One Product Backlog, One Product Owner rule, a Nexus integration group — to reduce cross-team dependencies and wasted work.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 5:03Horizontal Scaling
- 5:42Change in Focus
- 6:34Organizational Change
- 8:37Inverted Organization
- 9:12Agile
- 10:29Projectbased governance
- 13:34Scrum Studio
- 16:00Leadership Services
- 22:19Why Agile
- 25:00Technical Excellence
- 26:11Community
- 28:45Business Perspective
- 29:28Horizontal scaling challenges
- 33:27Crossteam dependencies
- 35:06Refactoring products
- 36:44Nexus
- 42:12Conclusion
- 44:24Summary
related talks
58mAgility at Scale: Tactical and Strategic Approaches
51mAgility at Scale: A Meeting of Mindsets
51mMastering Trade-offs for Scaled Agile Success
39mAgility at Scale: A Meeting of Mindsets
58mScaling Agile in Organizations
35mAgility at Scale: A Meeting of Mindsets
01h 04mBuilding big teams with Nexus
25mAgility at scale