Sabotaging a Transformation
summary
Claims agile yields 4–6x improvements versus a McKinsey 13% baseline, and teams run two-hour cycles with continuous delivery — one client ships 135 deployments in 2018 and triples that in 2020. Mitigations are concrete: use a pod for an eight‑week engagement (five weeks fixed price), train pair programming and TDD, build a C# microservice framework in days, change titles to a competence model, rearrange seating, secure an executive sponsor, and ignore or replace active gatekeepers who hoard knowledge.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:26Sabotage?
- 5:28Case: NAV Deployments
- 6:54Active saboteurs
- 13:47Active saboteurs mitigation
- 23:19Organizational sabotage
- 38:55Other types of sabotage
- 39:10Pod as a mitigation strategy
- 47:05Other mitigation techniques
- 50:40Outro
related talks
41mSabotaging an Agile Transformation
42mSabotaging a Transformation
01h 05mSabotaging a Transformation:Myriad Ways Organizations Inhibit Transformation
33mWhy You Should Not Start an Agile Transformation
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
18mAgile leadership and technical mastery, a harmonious alliance
45mWhy You Should not Start an Agile Transformation
36mOne Agile Transformation and two beers please
