View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Scrum |  Operations Waste Analysis |  Engineering Kanban |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-120 min | Ongoing |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Waste Map, Prioritized Waste, Improvement Backlog | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | AgileIterationCadence | WasteLeanProcess improvement | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
