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 |  Delivery Value Stream Mapping |  Decision Making Three-Point Estimation |
|---|---|---|---|
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 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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | Ongoing | 1-3 h | 10-30 min je Item |
Participantsdifferent | 2-12 | 4-10 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Three-Point Estimate, Risk Range, Assumption Notes |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | EstimationUncertaintyForecasting |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
