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 Theory of Constraints |  Operations Bottleneck Analysis |  Delivery Monte Carlo Forecasting |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | 2-4 h Analyse, laufend | 1-3 h | 30-90 min Setup, danach laufend | laufend |
Participantsdifferent | 3-12 | 3-8 | 1-8 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Forecast Percentiles, Throughput Dataset, Risk Communication | Throughput Data, Flow Forecast, Slicing Rules |
Tags1 shared | OperationsConstraintsFlowImprovement | FlowMeasurementConstraints | ForecastingFlowDelivery | EstimationForecastingFlow |