Do’s & Don’ts of Agile Transformations
summary
Distinguishes transition vs transformation and warns against planning agile like waterfall — you can’t fix mindset with a rigid plan. Gives concrete failures: forcing India teams onto UK hours created safety risks; a team improvised changes, got fired then rehired after management copied them. Recommends an incubator with separate HR and collective bonuses to prove value, measure value not per-bug counts, and scale teams slowly (don’t jump 1→20).
AI-written summary · about
chapters (4)
- 0:00Start
- 16:10Who Were the Change Influences with Your Company
- 28:27Game of Thrones
- 42:18Is Your Organization Supportive of Learning or Is It a Blank Culture
related talks
28mDos & Donts of Agile Transformations
24m5 Lessons Learned During Agile Transformations
43mNobody needs an Agile Transformation
36mAgile Déjà Vu – Why Do We Keep Failing at Transformations?
33mWhy You Should Not Start an Agile Transformation
23mIts transformation! But, is it though?
45mWhy You Should not Start an Agile Transformation
36mOne Agile Transformation and two beers please