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 Value Stream Mapping | ![]() Agile ROAM Board | ![]() Delivery Monte Carlo Forecasting | ![]() Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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 needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 h | 20-40 min initial, dann laufend | 30-90 min Setup, danach laufend | 30 min Setup, dann laufend |
Participantsdifferent | 4-10 | 3-15 | 1-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | ROAM Board, Owner List | Forecast Percentiles, Throughput Dataset, Risk Communication | RAID Log, Status Report Source |
Tagsno overlap | LeanFlowWasteDelivery | RiskAgileTrackingAlignment | ForecastingFlowDelivery | RiskTrackingStakeholdersGovernance |



