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 Monte Carlo Forecasting |  Decision Making Three-Point Estimation |  Delivery Value Stream Mapping |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | Ongoing | 30-90 min Setup, danach laufend | 10-30 min je Item | 1-3 h |
Participantsdifferent | 2-12 | 1-8 | 1-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Forecast Percentiles, Throughput Dataset, Risk Communication | Three-Point Estimate, Risk Range, Assumption Notes | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | FlowVisual managementDelivery | ForecastingFlowDelivery | EstimationUncertaintyForecasting | LeanFlowWasteDelivery |