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 |  Engineering Goal Question Metric |  Product Strategy Counter Metrics |
|---|---|---|---|
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 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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 90-180 min | 30-60 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | GQM Table, Metric Profiles | Counter Metric List, Guardrail Definitions |
Tagsno overlap | AgileIterationCadence | MetricsMeasurementEngineeringAlignment | MetricsMeasurementStrategyExperiments |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
