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 |  Agile Acceptance Criteria Workshop |  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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 20-40 min pro Story | 2-5 min je Item |
Participantsdifferent | 2-12 | 3-6 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Acceptance Criteria, Story Update | Relative Estimates, Assumption Notes, Split Candidates |
Tags1 shared | EstimationAgileRoadmap | AgileRequirementsRefinementBehavior-Driven Development | EstimationAgileRelative sizingTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
