Lean-Agile
Coaching and Training
Other
-
- Also some Useful Tools
Note that we have some Incomplete Pages That Require Work on this site:-)
Note that we have some Incomplete Pages That Require Work on this site:-)
Or “When Should We Use Kanban Instead of Scrum?”
Or “When Should We Use Scrum Instead of Kanban?”
The two most popular Team practices are Scrum and Kanban. People often wonder whether one is better than the other, or whether one should be applied over another. This page will help you think through the ideas.
Scrum | Kanban |
---|---|
Time-boxed iterations prescribed | Time-boxed iterations optional. * Can have separate cadences for planning, release, and process improvement. * Can be event driven instead of time-boxed. |
Team commits to a specific amount of work for this iteration (Sprint) | Team commits to work when it is brought to the board for execution |
Uses velocity as default metric for planning and process improvements | Uses lead (or cycle) time as default metric for planning and process improvements |
Cross functional teams prescribed | Cross functional teams optional * Specialist teams allowed |
Items must be broken down so they can be completed in an iteration | No item size is prescribed |
Burn down chart is prescribed | No diagram type is presecribed |
“Change agent” is commitment | “Change agent” is WIP limits |
WIP limited indirectly * Per iteration | WIP limited directly * Per workflow state |
Estimation prescribed | Estimation optional |
Cannot add items to ongoing iteration | Can add items whenever capacity is available |
Prescribe 3 roles * Product Owner * Scrum Master * Team | No prescribed roles |
Prescribes 4 ceremonies * Planning * Daily Scrum * Review * Retrospective | No prescribed ceremonies |
Scrum board is reset between each iteration | Kanban board is persistent |
Prioritized backlog is prescribed | Prioritization is optional |
Question | Kanban | Scrum |
---|---|---|
Primary Consideration | ||
* Work for the team is more than 50% demand driven (team's priority is responsiveness) | X | |
* Work for the team is most project driven (team's responsibility is predictability, forecasting and productivity) | X | |
Secondary Consideration | ||
* Team questions value of estimation and planning | X | |
* Team struggles to break items into small pieces | X | |
* No or low appetite for significant process change | X | |
* Some or high appetite for significant process change | X | |
* Team members have significant self-discipline | X | |
* Team members have limited self-discipline | X |