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 T-Shirt Sizing |  Agile Planning Poker |  Agile Affinity Estimation |
|---|---|---|---|---|
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 only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 15-45 min | 2-5 min je Item | 30-90 min |
Participantsdifferent | 3-8 | 2-12 | 3-9 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Size Buckets, Rough Backlog Map, Split Candidates | Relative Estimates, Assumption Notes, Split Candidates | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | FlowMeasurementConstraints | EstimationAgileRoadmap | EstimationAgileRelative sizingTeam | EstimationBacklogRelative sizing |