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 Example Mapping |  Agile Story Points |  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 carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | 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 | Low | Medium | Low |
Timedifferent | 15-45 min | 30-60 min | laufend, 1-5 min je Item | 2-5 min je Item |
Participantsdifferent | 2-12 | 3-7 | 3-9 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Example Map, Acceptance Criteria, Open Questions | Point Estimates, Reference Stories, Velocity Data | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationAgileRoadmap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EstimationAgileMeasurement | EstimationAgileRelative sizingTeam |