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 WSJF | ![]() Facilitation Dot Estimation | ![]() Delivery Monte Carlo Forecasting | ![]() Delivery Value Stream Mapping |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | 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. | 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 | High | Low | High | Medium |
Timedifferent | 45-90 min | 5-20 min | 30-90 min Setup, danach laufend | 1-3 h |
Participantsdifferent | 3-10 | 3-20 | 1-8 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Effort Heatmap, Risk Signals, Discussion Targets | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | LeanEconomicsSequencePrioritization | EstimationEffortRisk | ForecastingFlowDelivery | LeanFlowWasteDelivery |



