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 Ideal Days |  Agile Specification by Example |  Agile Example Mapping |  Agile Story Points |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-60 min | 60-90 min pro Feature | 30-60 min | laufend, 1-5 min je Item |
Participantsdifferent | 2-9 | 3-6 | 3-7 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Point Estimates, Reference Stories, Velocity Data |
Tagsno overlap | EstimationEffortAgile | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EstimationAgileMeasurement |