Why You Should not Start an Agile Transformation
summary
Claims that Agile always improves output get tested against messy specifics: Scrum and Kanban rollouts trigger a months‑long chaos phase where productivity can drop, training plus coaches and psychotherapists get used as remedies, and one cited case involves 300 people in chaos for one year with about 30% left. Advice: prepare a financial buffer, guarantee no immediate layoffs, run targeted training and global retrospectives, and measure real product metrics rather than promised percent gains.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:13Why companies start agile
- 2:37Myth of agile productivity
- 5:28System resistance before change
- 8:04Systems protect equilibrium
- 11:14Creating discomfort to break status quo
- 13:21Entering chaos phase
- 16:38Bad advice worsens chaos
- 19:03Surviving chaos phase
- 21:59Integration after chaos
- 25:56Early results harm progress
- 27:01Safe-to-fail training
- 29:28Signs of stable agile
- 31:35Maintaining new culture
- 33:29Celebrating improvement
- 34:35Question and answer session
related talks
33mWhy You Should Not Start an Agile Transformation
44mDragging out and failing Agile Transformation – reasons
43mNobody needs an Agile Transformation
01h 04mIs Agile Still the Answer? Lessons from Real World Agility
51mSabotaging a Transformation
43mWhy Agile transformation fail
34mFor effectiveness, Agile was never the answer
25mHow to get your derailed agile transformation back on track