View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Bottleneck Analysis |  Agile Story Points |  UX Research HEART Framework |  Engineering Goal Question Metric |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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 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. | 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 | Medium |
Timedifferent | 1-3 h | laufend, 1-5 min je Item | 120 min initial, dann laufend | 90-180 min |
Participantsdifferent | 3-8 | 3-9 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Point Estimates, Reference Stories, Velocity Data | HEART-GSM Table, Dashboard | GQM Table, Metric Profiles |
Tags1 shared | FlowMeasurementConstraints | EstimationAgileMeasurement | MetricsUX researchMeasurementSatisfaction | MetricsMeasurementEngineeringAlignment |