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 Planning Poker |  Team Design Spotify Model Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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 a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 2-5 min je Item | 90-180 min | 60–90 min |
Participantsdifferent | 3-9 | 5-15 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Spotify Model Map, Action List | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | EstimationAgileRelative sizingTeam | TeamOrganizationAlignmentDiagnosis | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
