How to get your derailed agile transformation back on track
summary
Starts by diagnosing with numbers not buzzwords: 41% of organizations are not satisfied and leadership lapses are concrete — 68% cite low leadership participation, 46% cite inadequate management support. Four anti‑patterns appear with fixes: partial agile / water‑scrum‑fall (map dependencies and combine suppliers), subverted (celebrate small wins), dishonest (reintroduce coaching and pilots), corrupted (give teams autonomy). Emphasis on measurable outcomes, retrospectives at all levels, and small experiments that show whether changes actually move delivery metrics.
AI-written summary · about
chapters (4)
- 0:00Derailed agile transformations
- 3:24Assessing transformation efforts
- 12:01Anti-patterns in agile adoption
- 21:48Resetting transformation goals
related talks
22m7 steps to destroy an Agile Transformation
40mRegain Benefits from Agile Software Development
51mManaging Agile: Transforming the Three Dysfunctions of Management
48mAgile is STILL a Dirty Word!
36mOne Agile Transformation and two beers please
05mFrAgile - lessons from a failed agile transformation
33mWhy You Should Not Start an Agile Transformation
44mDragging out and failing Agile Transformation – reasons
