Why You Should Not Start an Agile Transformation
summary
Claims that agile yields four hundred percents improvement get tested against a realistic change curve and a Satir-style transformation model, showing long chaotic drops, hiring of consultants, and political games. Concrete tools named: Scrum and Kanban, training, mentoring, hiring psychotherapists, and engineering practices like CI/CD. Surprising outcomes include deep short-term performance loss, mass turnover, and the need for psychological safety and safe-to-fail experiments before any sustained gain.
AI-written summary · about
chapters (12)
- 0:00Intro
- 4:32Status Quo
- 7:25Agile
- 13:23Cow smart
- 14:13Cow mode
- 16:19How to make situation worse
- 18:17What you can do
- 22:52The honeymoon period
- 24:24How to make it worse
- 25:11What you could do
- 30:12What you could not do
- 31:45Bossed
related talks
45mWhy You Should not Start an Agile Transformation
51mSabotaging a Transformation
24m5 Lessons Learned During Agile Transformations
43mNobody needs an Agile Transformation
28mDos & Donts of Agile Transformations
22m7 steps to destroy an Agile Transformation
36mOne Agile Transformation and two beers please
45mDo’s & Don’ts of Agile Transformations