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 Example Mapping |  Agile T-Shirt Sizing |  Agile Specification by Example |  Agile Ideal Days |
|---|---|---|---|---|
Purposedifferent | 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 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 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 | 30-60 min | 15-45 min | 60-90 min pro Feature | 15-60 min |
Participantsdifferent | 3-7 | 2-12 | 3-6 | 2-9 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Size Buckets, Rough Backlog Map, Split Candidates | Example Table, Acceptance Tests | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EstimationAgileRoadmap | AgileRequirementsExamplesBehavior-Driven Development | EstimationEffortAgile |