Nobody needs an Agile Transformation
summary
Argues that organisations do not need an “Agile transformation” as a methodology but must shift to outcomes over outputs, with leadership owning goals, strategies and metrics (use OKRs) while teams own delivery metrics like cycle time. Gives concrete failures: a PC client built to a spec that missed the true customer need, bonus-driven targets that overload testers and create silos, and the Standish finding that top success factors are cultural not process. Warns against Jira-driven vanity metrics.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 0:40Theodore Levitt
- 1:12The language of Agile
- 2:41When a transformation starts
- 3:56Agile software development
- 5:38Agile on the beach
- 6:19lbert agile
- 7:28problem with numbers
- 9:02motivation and challenge
- 11:18autonomy with alignment
- 13:18outcomes not outputs
- 13:33drilling analogy
- 14:15what is an outcome
- 15:25the biggest challenge
- 15:48three questions
- 19:14examples
- 22:43measure
- 25:04outputs
- 26:44culture eats strategy
- 27:20Success factors
- 29:26Objectives
- 31:07Visualization
- 33:38Unintended Outcomes
- 34:23Cultural Change
- 34:38Agile
- 34:58Its all about you
- 37:52Everything is Agile
- 38:11Leadership
- 39:04Education
- 39:58Transformational Leaders
- 41:20Summary
related talks
29mFrom Agile to Outcome-Driven
22m7 steps to destroy an Agile Transformation
33mWhy You Should Not Start an Agile Transformation
45mWhy You Should not Start an Agile Transformation
45mDo’s & Don’ts of Agile Transformations
36mOne Agile Transformation and two beers please
34mFor effectiveness, Agile was never the answer
43mAgile Outside Technology