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 |  Delivery RAID Log |  Agile NoEstimates |  Facilitation Dot Estimation |
|---|---|---|---|---|
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. | 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. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | laufend | 5-20 min |
Participantsdifferent | 4-10 | 1-3 maintaining, briefing for everyone | 2-12 | 3-20 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | RAID Log, Status Report Source | Throughput Data, Flow Forecast, Slicing Rules | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | LeanFlowWasteDelivery | RiskTrackingStakeholdersGovernance | EstimationForecastingFlow | EstimationEffortRisk |