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 Specification by Example |  Agile Story Points |  Facilitation Dot Estimation |  Agile Ideal Days |
|---|---|---|---|---|
Purposedifferent | 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 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. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | 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 | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | laufend, 1-5 min je Item | 5-20 min | 15-60 min |
Participantsdifferent | 3-6 | 3-9 | 3-20 | 2-9 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Point Estimates, Reference Stories, Velocity Data | Effort Heatmap, Risk Signals, Discussion Targets | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | EstimationAgileMeasurement | EstimationEffortRisk | EstimationEffortAgile |