View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Dot Estimation |  Operations Bottleneck Analysis |  Agile Planning Poker |  Agile Story Points |
|---|---|---|---|---|
Purposedifferent | 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. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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 | Low | Medium | Low | Medium |
Timedifferent | 5-20 min | 1-3 h | 2-5 min je Item | laufend, 1-5 min je Item |
Participantsdifferent | 3-20 | 3-8 | 3-9 | 3-9 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Relative Estimates, Assumption Notes, Split Candidates | Point Estimates, Reference Stories, Velocity Data |
Tagsno overlap | EstimationEffortRisk | FlowMeasurementConstraints | EstimationAgileRelative sizingTeam | EstimationAgileMeasurement |