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 |  Delivery RAID Log |  Decision Making PERT Estimation |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 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 | 30 min Setup, dann laufend | 15-45 min | 5-20 min |
Participantsdifferent | 3-9 | 1-3 maintaining, briefing for everyone | 1-8 | 3-20 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | RAID Log, Status Report Source | PERT Estimate, Expected Value, Risk Notes | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | EstimationAgileMeasurement | RiskTrackingStakeholdersGovernance | EstimationUncertaintyRisk | EstimationEffortRisk |