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 |  Engineering Goal Question Metric |
|---|---|---|---|
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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | laufend, 1-5 min je Item | 15-45 min | 90-180 min |
Participantsdifferent | 3-9 | 1-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | PERT Estimate, Expected Value, Risk Notes | GQM Table, Metric Profiles |
Tagsno overlap | EstimationAgileMeasurement | EstimationUncertaintyRisk | MetricsMeasurementEngineeringAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
