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 |  Agile Ideal Days |  Agile T-Shirt Sizing |  Agile NoEstimates |
|---|---|---|---|---|
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. | 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. | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 15-60 min | 15-45 min | laufend |
Participantsdifferent | 3-8 | 2-9 | 2-12 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Size Buckets, Rough Backlog Map, Split Candidates | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | FlowMeasurementConstraints | EstimationEffortAgile | EstimationAgileRoadmap | EstimationForecastingFlow |