View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Dual-Track Agile |  Delivery Monte Carlo Forecasting |  Delivery Value Stream Mapping |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | Laufend, Wochen bis Monate | 30-90 min Setup, danach laufend | 1-3 h | Ongoing |
Participantsdifferent | 4-10 | 1-8 | 4-10 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics |
Tags1 shared | AgileDiscoveryDelivery | ForecastingFlowDelivery | LeanFlowWasteDelivery | FlowVisual managementDelivery |