Kanban, our way
summary
Team migrates from Scrum to a customized Kanban on a GitHub board with weekly releases, triage and labels for kind/area/impact/gain, soft WIP limits, and a priority backlog separate from a large backlog; refinement uses Fibonacci story points and live voting to split >8s, standups run three times weekly, architecture meetings use a five‑minute per‑topic timer, retros are biweekly, and roles rotate (including rotating Kanban Lead and service guru); this setup reduces single‑point failures, increases knowledge sharing, and keeps flow despite Jira sync limitations.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 1:47Kanban board overview
- 4:59Weekly meetings
- 8:19Standup details
- 12:33Architecture meetings
- 16:26Retrospective
- 17:32Team roles
- 21:36Q&A
related talks
35mMy journey from misshapen Scrum to reliable Kanban
21mCase study - A journey from Scrum to Kanban
45mPortofolio Kanban, The Art of Being Loosely Coupled and Highly Aligned
31mHow we used Kanban in Operations to Get Things Done
01h 27mPNSQC 2014 - Halim Dunsky
50mSuccess factors: Why am I using Scrum or Kanban
43mApplying Agile out of development
10mEffective TODO selection: A Kanban story