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 Scrum |  Delivery Monte Carlo Forecasting |  Delivery Value Stream Mapping |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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 | Medium | High | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-90 min Setup, danach laufend | 1-3 h |
Participantsdifferent | 3-10 (Scrum Team) | 1-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | AgileIterationCadence | ForecastingFlowDelivery | LeanFlowWasteDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
