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 |  Decision Making PERT Estimation |  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. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. | 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 | Medium | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 15-45 min | 60-90 min pro Feature | 5-20 min |
Participantsdifferent | 3-9 | 1-8 | 3-6 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | PERT Estimate, Expected Value, Risk Notes | Example Table, Acceptance Tests | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | EstimationAgileMeasurement | EstimationUncertaintyRisk | AgileRequirementsExamplesBehavior-Driven Development | EstimationEffortRisk |