Turbocharge your Scrum
summary
Claims that 58% of Scrum rollouts fail lead to a concrete fix: apply Kanban practices on top of Scrum, not replace it. Start with the current process, add per-person WIP limits, visualize end-to-end flow with a big board and explicit policies, use lead time histogram and cumulative flow diagrams, switch from task estimates to t-shirt sizing and replenishment meetings and SLAs. Case data shows dramatic gains—one team posts a 90% improvement in lead time in ~90 days and others report 4x or ~20x throughput gains.
AI-written summary · about
chapters (18)
- 0:00Start
- 8:31Kanban is not a framework
- 13:04Start with what you do now
- 14:09Agree to evolutionary change
- 16:18Encourage acts of leadership at all level
- 17:42Visualize
- 20:09Limit Work in Progress
- 21:07Manage Flow
- 23:54Make Policies Explicit
- 24:56Feedback and Feedback Loops
- 30:06Feedback Loop?
- 34:41Posit Science Background
- 36:10Initial "Kanban" adoption
- 38:01Goals of new "flow" system
- 38:15Transition to "flow"
- 38:59Replenishment Meeting Board
- 41:27Team P: Flow Metrics
- 43:50Kanban Impact at Accenture Brazil
related talks
30mTaming the Chaos: Beyond the Quick Wins
21mCase study - A journey from Scrum to Kanban
33mTaming The Chaos: After The Quick Wins
34mThinking more product: Moving from Scrum to dual-track Agile
34mFrom Waterfall To River – A Story Of Transitioning To Flow
46mScrum & Lean Startup in Action: Design to Delivery in 6 Months
41mAre You Failing at Being Agile?
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum