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 |  Delivery Monte Carlo Forecasting |  Product Strategy DIBB |  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. | 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. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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 | High | Low | Medium |
Timedifferent | 45-90 min | 30-90 min Setup, danach laufend | 1-2 h | 1-3 h |
Participantsdifferent | 3-10 | 1-8 | 2-8 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Forecast Percentiles, Throughput Dataset, Risk Communication | DIBB document, Belief list, Bet list, Learning report | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | LeanEconomicsSequencePrioritization | ForecastingFlowDelivery | StrategyDecisionAssumptionsHypothesis | LeanFlowWasteDelivery |