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 Planning Poker |
|---|---|---|---|
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 1-3 h | 2-5 min je Item |
Participantsdifferent | 2-12 | 3-8 | 3-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationAgileRoadmap | FlowMeasurementConstraints | EstimationAgileRelative sizingTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
