Mastering Trade-offs for Scaled Agile Success
summary
Argues that scaling agile requires trading individual resource efficiency for system-level flow and shows concrete fixes: switch from asynchronous bug tickets to immediate joint troubleshooting which delivers features faster; apply WIP limits at every level, track blockers (one category accounts for almost 50% of stalls), visualize work on a giant wall for ~2,500 people and use a program board and PI cadence (~12 weeks) to manage dependencies, enabling bigger feature teams (up to ~20) and measurable faster delivery.
AI-written summary · about
chapters (15)
- 0:00Scaling agile trade-offs
- 2:16Busy teams slow delivery
- 8:22Efficiency vs flow in dev
- 11:40Systems thinking for agile
- 14:09Kanban and Scrum together
- 16:16WIP limits across levels
- 20:33Visualizing work for flow
- 24:09Process improvements from deviations
- 28:05Blockers as improvement gold
- 28:27Cadence vs synchronization trade-offs
- 30:39Avoiding component dependencies
- 34:01Dependencies with program boards
- 37:12Continuous delivery beyond PI
- 39:12Systems for good performance
- 41:23Q&A
related talks
58mScaling Agile in Organizations
58mAgility at Scale: Tactical and Strategic Approaches
47mThe Only 2 Things needed to Scale Agile
47m7 Sins of Scaling and Other Agile Anti Patterns
43mMind the gap – incorporating the change agenda into scaled Agile.
48mTwo Dimensions Of Agile At Scale
50mWhy Agile Doesn't Scale & What You Can Do About It
51mAgility at Scale: A Meeting of Mindsets