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 |  Agile Planning Poker |  Facilitation Alignment Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 2-5 min je Item | 1-2 h | 60-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-9 | 4-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Relative Estimates, Assumption Notes, Split Candidates | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | TeamAlignmentCommunicationService | EstimationAgileRelative sizingTeam | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |