Dos & Donts of Agile Transformations
summary
Defines transformation vs transition, warns against avoid waterfall plans for change by showing why fixed timelines and certainty fail, and argues for engaging HR and people (not “resources”) early. Uses a Chinese‑whisper exercise and real cases — shifting Indian team hours that endangered staff, scaling one team into 40 broken teams — to force practical lessons: measure value not hours, pick actual change influencers, build internal capability, run small experiments and only scale once patterns prove repeatable.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:18Transformation vs Transition
- 4:02Waterfall vs Agile
- 8:53Dualities
- 11:42Resources
- 16:25Chinese Whisper
- 20:39Calm Strategy
- 21:17Change Influences
- 22:20Game of Thrones
- 24:29Internal Capabilities
- 25:22Too Early
- 27:02Outro
related talks
45mDo’s & Don’ts of Agile Transformations
26mAgile Transformations are not about software
24m5 Lessons Learned During Agile Transformations
23mIts transformation! But, is it though?
45mAgile Transformation Or Just Another Restructure?
36mAgile Déjà Vu – Why Do We Keep Failing at Transformations?
33mWhy You Should Not Start an Agile Transformation
43mTaking Agile to the Enterprise – strategy lessons from seven years in transformation