View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Engineering Goal Question Metric |  Facilitation Power Interest Grid |
|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 90-180 min | 30-60 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | GQM Table, Metric Profiles | Power Interest Grid, Strategy per Stakeholder |
Tags1 shared | TeamAlignmentCommunicationService | MetricsMeasurementEngineeringAlignment | StakeholdersFacilitationAlignmentPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
