Why Scrum Fails: It’s a System Problem, Not a Team Problem
summary
The talk argues Scrum fails not because teams lack will but because organizational systems reward control, obedience, and predictability. It gives concrete examples — a CEO acting as product manager causing six‑month releases and long hardening sprints, a Kanban trial that increases WIP and blocks flow, and per‑page redesign bonuses that boost speed but increase defects — and recommends changing incentives and informal influence networks, asking teams how to meet goals, and practicing system‑level changes plus values like vulnerability, empathy, integrity, and adaptability.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:30Small Scrum failures
- 2:52Two organizational structures
- 5:04Scrum failure stories
- 10:23Why change fails
- 11:05Tilt the change cycle
- 12:10Authenticity journey
- 17:28Four pillars of authenticity
- 22:43Change the environment
- 24:11Group discussion
- 33:40Final thoughts and Q&A
