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 Story Points |  Delivery Value Stream Mapping |  Facilitation Dot Estimation |  Operations Bottleneck Analysis |
|---|---|---|---|---|
Purposedifferent | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | 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 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. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | laufend, 1-5 min je Item | 1-3 h | 5-20 min | 1-3 h |
Participantsdifferent | 3-9 | 4-10 | 3-20 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Current-state map, Future-state map, Bottleneck list | Effort Heatmap, Risk Signals, Discussion Targets | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | EstimationAgileMeasurement | LeanFlowWasteDelivery | EstimationEffortRisk | FlowMeasurementConstraints |