Is Agile Still the Answer? Lessons from Real World Agility
summary
Traces real outcomes: Kanban boards and cycle‑time scatter plots show nearly doubled throughput for one team and a 50% increase in completed items for another, but digging reveals artificial slicing inflating numbers; an internal team‑health app ships with poor NPS; a portfolio Kanban cuts WIP and shortens average project time; probabilistic burnup forecasting replaces single dates; a built sneaker‑raffle (ASOS Drops) ties work to revenue. Concrete tools, counts and failures decide whether agility works.
AI-written summary · about
chapters (10)
- 0:00Real-world agility lessons
- 7:25Agile history and evolution
- 10:13Flow and Kanban boards
- 14:08Measuring throughput and cycle time
- 24:04Leading vs lagging metrics
- 27:56Aligning work with strategy
- 37:25Culture and psychological safety
- 48:01Delivery with forecasting
- 56:57Is Agile still the answer?
- 1:03:05Q&A
related talks
38mBenefits of Agility at Scale
48mAgile is STILL a Dirty Word!
46mAgile: principles over practices
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
45mWhy You Should not Start an Agile Transformation
50mAgile Outside IT Companies & Departments: Real Stories of Transformations
43mAgile Outside Technology
44mMeasuring agility: Data analytics ex psychology to grow your teams agility