View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Agile Scrum |  Delivery Value Stream Mapping |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | Ongoing | 1-4 Wochen je Sprint, laufend | 1-3 h | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 3-10 (Scrum Team) | 4-10 | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Current-state map, Future-state map, Bottleneck list | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | AgileIterationCadence | LeanFlowWasteDelivery | ForecastingFlowDelivery |