The following table (thanks to Alin) was compiled to get an fast overview on the 3 mostly used agile approaches – Scrum, Kanban and the combination of both Scrumban.
Maybe you’re currently thinking about your environment and what agile method to use. Use this list to support your decision.
| Scrum | Kanban | Scrumban | |
|---|---|---|---|
| Board/Artifacts | simple board product backlog sprint backlog product increment burndown chart |
board mapped on the process | board mapped on the process |
| Ceremonies | daily Scrum sprint planning sprint review sprint retrospective |
none required | daily Scrum other Scrum related ceremonies if needed |
| Prioritization | Part of backlog grooming. Done by PO | Out of the process. There should be a prioritized backlog. | Out of the process. There should be a prioritized backlog. |
| Who feeds the work in progress (“brings new work”) | PO | Depends on defined roles and necessities | Depends on defined roles and necessities |
| Iterations | yes (sprints) | no (continuous flow) | not mandatory (continuous flow); could have sprints |
| Estimations | yes (in ideal days or story points) | no (similar work size items) (a) | no (similar work size items) (a) |
| Teams | recommended cross functional | cross functional or specialized | cross functional or specialized |
| Roles | Product Owner Scrum Master Team |
as needed | Team + as needed |
| Teamwork | collaborative | based on pull approach | based on pull approach |
| WIP | planned for the duration of the sprint | controlled by workflow state | controlled by workflow state |
| changes to work scope | should wait for next sprint | added as needed (JIT) | added as needed (JIT) |
| Product backlog | prioritized list of user stories (estimated) | no (JIT) | no (JIT) |
| Impediments | addressed immediately | addressed immediately (b) | addressed immediately (b) |
| When does it fit? | Product development Small value adding increments development possible Requirements are in good shape |
Support/maintenance work (operational level) | Product development (unclear vision) Evolving requirements (no clear roadmap) Need to include support/maintenance (event driven) work in the process |
(a) team needs to comment on non-fitting work items in order to ensure readiness
(b) “stop the line” approach; teams should swarm to solve the impediment
Update 2015-03-12 – Scrum and ScrumBan as it’s next evolutionary step … and is it wort starting Scrum at all
Leave a Reply