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 Story Points |  Agile Specification by Example |
|---|---|---|---|
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 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | laufend, 1-5 min je Item | 60-90 min pro Feature |
Participantsdifferent | 2-12 | 3-9 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Point Estimates, Reference Stories, Velocity Data | Example Table, Acceptance Tests |
Tags1 shared | EstimationAgileRoadmap | EstimationAgileMeasurement | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
