View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Bottleneck Analysis |  Facilitation Dot Estimation |  Agile NoEstimates |  Agile Story Points |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 5-20 min | laufend | laufend, 1-5 min je Item |
Participantsdifferent | 3-8 | 3-20 | 2-12 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Effort Heatmap, Risk Signals, Discussion Targets | Throughput Data, Flow Forecast, Slicing Rules | Point Estimates, Reference Stories, Velocity Data |
Tagsno overlap | FlowMeasurementConstraints | EstimationEffortRisk | EstimationForecastingFlow | EstimationAgileMeasurement |