Agile Transformation Or Just Another Restructure?
summary
Checklist and prescription for an actual transformation versus a paperwork restructure: organizations hire consultants, produce playbooks, redesign org charts into squads/tribes/chapters, rename roles, run a big-bang rollout with training and change comms, then claim outcomes like double our velocity while cutting hundreds of roles. Alternative: make a clear why, map customer value streams, split work into agility streams, prioritize with weighted shortest job first, deliver small measurable outcomes, baseline real metrics (happiness, revenue), iterate and adapt.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 2:50Engage Consultants
- 3:40Create Plans
- 4:20Create Documents
- 5:03Design the Structure
- 6:00Redefine Roles
- 7:42Define Ways of Working
- 9:08Make Announcements
- 10:33Adoption Phase
- 11:23Waterfall
- 11:52Thinking at the beginning
- 12:48We end up with meaningless measurement
- 14:06Speed is the perfect example
- 14:53Emotional attachment
- 15:36Politics
- 16:10Agile Manifesto
- 17:01What could go wrong
- 18:06Worry and anxiety
- 18:57Fear uncertainty and doubt
- 20:12No accountability
- 20:41Escalation
- 21:33What can go wrong
- 22:31How can you transform
- 23:12Clarity on why
- 25:39Agility streams
- 27:37Customer value streams
- 28:54Include all the people
- 30:13Break it down into smaller outcomes
- 31:34Prioritize
- 32:30Measure
- 33:35Small Change
- 34:37Review Your Backlog
- 35:45Rinse Repeat
- 36:52Team vs Individual
- 37:29Development Manager Role
related talks
28mDos & Donts of Agile Transformations
36mOne Agile Transformation and two beers please
48mDesigning Our Agile Transformation Strategy
23mIts transformation! But, is it though?
33mWhy You Should Not Start an Agile Transformation
43mScrew Agile transformation, transform yourself instead!
06mEnterprise Transformation
43mTaking Agile to the Enterprise – strategy lessons from seven years in transformation