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 Acceptance Criteria Workshop | ![]() Agile Specification by Example |
|---|---|---|---|
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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 |
Timedifferent | 15-60 min | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 2-9 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tags1 shared | EstimationEffortAgile | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






