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 |  Facilitation Expectation Mapping |  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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | laufend, 1-5 min je Item | 45-90 min | 90-180 min |
Participantsdifferent | 3-9 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Expectation Map, Alignment Notes, Agreements | GQM Table, Metric Profiles |
Tagsno overlap | EstimationAgileMeasurement | AlignmentStakeholdersTeam | MetricsMeasurementEngineeringAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
