My journey from misshapen Scrum to reliable Kanban
summary
Team replaces misfitting Scrum/SAFe rituals with a Kanban system using STATIK, resets Jira to task-based issues, and defines classes of service and explicit policies. They impose WIP limits (from ~16 open items to 9) and add lightweight cadences: 15-minute daily board walk, biweekly reviews and replenishment. Measured results: average lead time drops from ~140 days to ~41 and median from ~50 to ~10 days. Third‑party release constraints remain and Kanban demands strict discipline.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 2:33My story
- 3:14Disclaimer
- 4:57Dismantled Scrum
- 5:52Problems with misshapen Scrum
- 10:05Product Items Added or Removed
- 11:29Brainstorming
- 12:55State of Canada Report
- 13:55What do I understand as Kanban
- 15:15The Kanban Guide
- 15:57Early Misconceptions
- 18:26The Final Question
- 18:42Static Kanban
- 19:51Conclusions
- 22:49Reshaping our work
- 23:35Limiting work in progress
- 25:06Managing the flow
- 25:59Explicit rules
- 27:22Experimentation
- 28:02Handling problems
- 29:18Discipline
- 29:45What I would do differently
- 31:05Teams reflection
- 31:59Kanban
- 32:36Our teams inspired others
