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 |  Operations Theory of Constraints |  Delivery Monte Carlo Forecasting |  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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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 | High | High | Medium |
Timedifferent | laufend, 1-5 min je Item | 2-4 h Analyse, laufend | 30-90 min Setup, danach laufend | 1-3 h |
Participantsdifferent | 3-9 | 3-12 | 1-8 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Constraint Map, Improvement Plan, Flow Metrics | Forecast Percentiles, Throughput Dataset, Risk Communication | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | EstimationAgileMeasurement | OperationsConstraintsFlowImprovement | ForecastingFlowDelivery | FlowMeasurementConstraints |