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 Specification by Example |  Agile Bucket System |  Agile Affinity Estimation |
|---|---|---|---|---|
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 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. | When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 60-90 min pro Feature | 30-90 min | 30-90 min |
Participantsdifferent | 2-12 | 3-6 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Example Table, Acceptance Tests | Bucketed Backlog, Relative Estimates, Split Candidates | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | EstimationAgileRoadmap | AgileRequirementsExamplesBehavior-Driven Development | EstimationBacklogRelative sizing | EstimationBacklogRelative sizing |