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 |  Operations ABC Analysis |  Agile Planning Poker |  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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 30-60 min | 2-5 min je Item | laufend, 1-5 min je Item |
Participantsdifferent | 3-8 | 1-5 | 3-9 | 3-9 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | ABC Classification, Focus Rules, Control List | Relative Estimates, Assumption Notes, Split Candidates | Point Estimates, Reference Stories, Velocity Data |
Tagsno overlap | FlowMeasurementConstraints | PrioritizationOperationsPortfolio | EstimationAgileRelative sizingTeam | EstimationAgileMeasurement |