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 |  Delivery Value Stream Mapping |  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. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | Ongoing |
Participantsdifferent | 3-10 (Scrum Team) | 4-10 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | AgileIterationCadence | LeanFlowWasteDelivery | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
