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 Specification by Example |  Agile Ideal Days |
|---|---|---|---|---|
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 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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30-60 min | 60-90 min pro Feature | 15-60 min |
Participantsdifferent | 2-12 | 3-7 | 3-6 | 2-9 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | EstimationAgileRoadmap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | EstimationEffortAgile |