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 Bucket System |  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 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 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 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 | Low | Medium | Medium |
Timedifferent | 15-45 min | 30-60 min | 30-90 min | 60-90 min pro Feature |
Participantsdifferent | 2-12 | 3-7 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Example Map, Acceptance Criteria, Open Questions | Bucketed Backlog, Relative Estimates, Split Candidates | Example Table, Acceptance Tests |
Tagsno overlap | EstimationAgileRoadmap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EstimationBacklogRelative sizing | AgileRequirementsExamplesBehavior-Driven Development |