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 Bottleneck Analysis | ![]() Agile Bucket System |
|---|---|---|---|
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 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 a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 1-3 h | 30-90 min |
Participantsdifferent | 2-12 | 3-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Bucketed Backlog, Relative Estimates, Split Candidates |
Tagsno overlap | EstimationAgileRoadmap | FlowMeasurementConstraints | EstimationBacklogRelative sizing |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






