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 Story Points |  Agile Ideal Days |  Agile Specification by Example |  Facilitation Dot Estimation |
|---|---|---|---|---|
Purposedifferent | 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 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 15-60 min | 60-90 min pro Feature | 5-20 min |
Participantsdifferent | 3-9 | 2-9 | 3-6 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Example Table, Acceptance Tests | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | EstimationAgileMeasurement | EstimationEffortAgile | AgileRequirementsExamplesBehavior-Driven Development | EstimationEffortRisk |