Difference between Kanban and Scrum:
- Iterations : Kanban sees development as a forever ongoing flow of things to do where as in Scrum you work in iterations.
- Commitment : Kanban is ongoing where as in Scrum a team commits to what they will do during a sprint.
- Estimations : In Kanban it’s optional since focus is on time-to-market. In Scrum you need to estimate to be able to have a velocity.
- Cross-functional teams : That’s one of the pillars of Scrum. For Kanban it’s optional.
- Workflow : The Kanban Method does not prescribe any workflow. Scrum prescribes a set of activities that are performed within a Sprint.
- Roles : Kanban does not prescribe any roles. Scrum generally prescribes three roles, Scrum Master, Product Owner, and Team Member.
- System Thinking : The Kanban Method takes a system thinking approach to process problems. Scrum is team-centric.
| Kanban | Scrum | |
| Board / Artifacts | board only | board, backlogs, burn-downs |
| Ceremonies | daily scrum, review/retrospeective on set frequency and planning ongoing | daily scrum, sprint planning, spring review, sprint retrospective |
| Iterations | no (continuous flow) | yes (sprints) |
| Estimation | no (similar size) | yes |
| Teams | can be specialized | must be cross-functional |
| Roles | Team + need roles | Product Owner, Scrum Master, Team |
| Teamwork | swarming to achieve goals | collaborative as needed by task |
| WIP | controlled by worklfow state | controlled by sprint content |
| Changes | added as nedded on the borad (to do) | should wait for the next sprint |
| Product Backlog | just in time cards | list of prioritized and estimated stories |
| Impediments | avoided | dealt with immediately |
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.