View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Product Discovery Dual-Track Agile |  Delivery Value Stream Mapping |  Operations Waste Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Ongoing | Laufend, Wochen bis Monate | 1-3 h | 45-120 min |
Participantsdifferent | 2-12 | 4-10 | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Current-state map, Future-state map, Bottleneck list | Waste Map, Prioritized Waste, Improvement Backlog |
Tagsno overlap | FlowVisual managementDelivery | AgileDiscoveryDelivery | LeanFlowWasteDelivery | WasteLeanProcess improvement |