Agile Déjà Vu – Why Do We Keep Failing at Transformations?
summary
Argues that most transformations fail because organisations swap values and principles for checklists and add meetings that create administrative overhead, citing 70% of initiatives fail from cited studies; shows how decisions made top-down without clear goals or competent hires produce a flipped “pyramid of impediments”; demonstrates simple experiments (blank slide, dog anecdotes, Shrek onion) to reveal context gaps; recommends concrete fixes: start with clear purpose, visualise work for transparency, hire for outcomes and facilitation skills instead of searching for a superhero, and support teams rather than micromanage.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:05What is agile transformation
- 3:14Transformation components and goals
- 6:27Change management lessons from dogs
- 8:16Transformation onion and context
- 11:11Why 70% of changes fail
- 13:19Focus on value not metrics
- 15:46Balancing leadership and team autonomy
- 17:55Top-down transformations pitfalls
- 20:23Myth of the perfect agile hire
- 21:49Culture makes or breaks transformation
- 22:51One-size-fits-all warning
- 23:55Danger of trend-driven transformations
- 24:38Pyramid of transformation impediments
- 27:10Q&A: Purpose in Scrum
- 29:01Q&A: Pushing meaningful change as engineer
- 35:24Closing remarks
related talks
23mIts transformation! But, is it though?
28mDos & Donts of Agile Transformations
45mDo’s & Don’ts of Agile Transformations
22m7 steps to destroy an Agile Transformation
51mManaging Agile: Transforming the Three Dysfunctions of Management
25mHow to get your derailed agile transformation back on track
36mOne Agile Transformation and two beers please
24m5 Lessons Learned During Agile Transformations