The Only 2 Things needed to Scale Agile
summary
Claim: scale adaptability by doing two specific things not adopting a framework. Move funding from projects to product-based portfolio management (example: bank story with a requested two million estimate vs range 1.3 / 1.9 / 2.9M and the PERT shortcut (best + 4×likely + worst)/6) and organize around autonomous feature teams that include business through ops. Fund capabilities not tasks, run small funded experiments (examples given: ~$200k or pilot ~$50k), decentralize decision-making, stop component teams that block feedback.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:19DON'T SCALE THE AGILE PROCESS
- 3:451 PROJECT FUNDING IS OUT
- 5:242 AUTONOMOUS FEATURE TEAMS
- 6:21CAN YOU FINISH ON TIME, ON
- 18:42WHAT IS MORE VALUABLE?
- 19:10WHY ARE YOU BUILDING THE FEATURE?
- 20:42ORGANISE AROUND PRODUCTS
- 30:00COMPONENTS TEAMS ARE NOT AGILE
- 30:21WORKING SOFTWARE OVER
related talks
58mAgility at Scale: Tactical and Strategic Approaches
51mMastering Trade-offs for Scaled Agile Success
58mScaling Agile in Organizations
50mWhy Agile Doesn't Scale & What You Can Do About It
39mAgility at Scale: A Meeting of Mindsets
51mAgility at Scale: A Meeting of Mindsets
43mMind the gap – incorporating the change agenda into scaled Agile.
35mAgility at Scale: A Meeting of Mindsets