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 Theory of Constraints |  Agile Story Points |  Agile Planning Poker |
|---|---|---|---|---|
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. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | 2-4 h Analyse, laufend | laufend, 1-5 min je Item | 2-5 min je Item |
Participantsdifferent | 3-8 | 3-12 | 3-9 | 3-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Constraint Map, Improvement Plan, Flow Metrics | Point Estimates, Reference Stories, Velocity Data | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | FlowMeasurementConstraints | OperationsConstraintsFlowImprovement | EstimationAgileMeasurement | EstimationAgileRelative sizingTeam |