View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Monte Carlo Forecasting |  Product Discovery Dual-Track Agile |  Delivery Value Stream Mapping |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 30-90 min Setup, danach laufend | Laufend, Wochen bis Monate | 1-3 h | 15-30 min |
Participantsdifferent | 1-8 | 4-10 | 4-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Current-state map, Future-state map, Bottleneck list | Root cause notes, Countermeasures |
Tagsno overlap | ForecastingFlowDelivery | AgileDiscoveryDelivery | LeanFlowWasteDelivery | Root causeIncidentLeanProblem solving |