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 T-Shirt Sizing |  Operations Theory of Constraints |  Operations Bottleneck Analysis |  Agile Ideal Days |
|---|---|---|---|---|
Purposedifferent | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | 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. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 15-45 min | 2-4 h Analyse, laufend | 1-3 h | 15-60 min |
Participantsdifferent | 2-12 | 3-12 | 3-8 | 2-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Constraint Map, Improvement Plan, Flow Metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | EstimationAgileRoadmap | OperationsConstraintsFlowImprovement | FlowMeasurementConstraints | EstimationEffortAgile |