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 |  Engineering Goal Question Metric |  Agile ROAM Board |  UX Research HEART Framework |
|---|---|---|---|---|
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 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | laufend, 1-5 min je Item | 90-180 min | 20-40 min initial, dann laufend | 120 min initial, dann laufend |
Participantsdifferent | 3-9 | 3-6 | 3-15 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | GQM Table, Metric Profiles | ROAM Board, Owner List | HEART-GSM Table, Dashboard |
Tagsno overlap | EstimationAgileMeasurement | MetricsMeasurementEngineeringAlignment | RiskAgileTrackingAlignment | MetricsUX researchMeasurementSatisfaction |