7 steps to destroy an Agile Transformation
summary
Seven concrete failure modes: no clear end goal so teams “do Agile” with no purpose; metrics explode or focus narrowly instead of measuring for purpose; inspection and adaptation barely happen (many teams never review OKRs, some only yearly); organizational silos persist; empowerment lacks constraints and is fixed with a delegation board; competence development and protected learning time are missing; one-size-fits-all adoption (Scrum everywhere) ignores domain fit. Cross-team initiatives and shared goals are the specific fix that repeatedly works.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:00Presentation
- 4:10Step 1 No vision
- 5:50Step 2 Future perspective
- 8:20Step 3 Metrics
- 9:15Management 30 Principles
- 10:55Inspection and Adaptation
- 11:40Review the whole process
- 12:40Working in silos
- 13:50Tribal leadership
- 15:25Empower people
- 17:45Competences
- 18:30Time
- 19:30Harmony Law
- 20:15The Canadian Framework
- 21:20Questions
related talks
25mHow to get your derailed agile transformation back on track
43mNobody needs an Agile Transformation
24m5 Lessons Learned During Agile Transformations
33mWhy You Should Not Start an Agile Transformation
05mFrAgile - lessons from a failed agile transformation
40mRegain Benefits from Agile Software Development
36mAgile Déjà Vu – Why Do We Keep Failing at Transformations?
23mIts transformation! But, is it though?