PNSQC 2014 - Halim Dunsky
summary
Compares scrum (fixed two‑ to three‑week iterations) with kanban (continuous flow), explains metrics and tooling like burn‑up, cumulative flow and Jira control charts, and argues for WIP limits and small batches to reduce multitasking. Gives concrete results from a telco: a rotating defect team processes 600 defect tickets in six weeks and cuts a later release backlog to about one‑tenth. Describes mixed models (rotating defect teams, defect subteams, kanban for external services) and emphasizes lead time and cycle time for predictability.
AI-written summary · about
chapters (15)
- 0:00Start
- 6:08Explicit Process Policies
- 7:18Sidebar: Minimum Viable Product
- 14:02Example Dimensions of Software Quality
- 17:12Focus on Working Software
- 21:50Reducing lag
- 35:54Scrum Roles
- 37:30How Does Scrum Work?
- 39:11Release Burup Chart
- 40:42Extending the Definition of Done
- 45:33Ken Schwaber on Scrum Values
- 49:06Kanban Queues - Example
- 51:41Work In Process Limits
- 52:57Setting WIP Limits
- 58:17Classes of Service
related talks
35mMy journey from misshapen Scrum to reliable Kanban
35mKanban, our way
32mHow Lean is your Scrum
46mThe Neverending Story: Agile Transformation for DevOps
30mTaming the Chaos: Beyond the Quick Wins
50mSuccess factors: Why am I using Scrum or Kanban
47mHow it goes to heck in a handbasket
33mTaming The Chaos: After The Quick Wins