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 |  Agile Planning Poker |  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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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 | Low | Medium |
Timedifferent | laufend, 1-5 min je Item | 2-5 min je Item | 1-3 h |
Participantsdifferent | 3-9 | 3-9 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Relative Estimates, Assumption Notes, Split Candidates | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | EstimationAgileMeasurement | EstimationAgileRelative sizingTeam | FlowMeasurementConstraints |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
