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 Scrum |  UX Research HEART Framework |  Agile Story Points |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 120 min initial, dann laufend | laufend, 1-5 min je Item |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 3-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | HEART-GSM Table, Dashboard | Point Estimates, Reference Stories, Velocity Data |
Tagsno overlap | AgileIterationCadence | MetricsUX researchMeasurementSatisfaction | EstimationAgileMeasurement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
