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 | ![]() Facilitation Alignment Mapping | ![]() Team Design Spotify Model 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 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 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 2-5 min je Item | 1-2 h | 90-180 min |
Participantsdifferent | 3-9 | 4-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Alignment Map, Open Issues, Decision Questions | Spotify Model Map, Action List |
Tagsno overlap | EstimationAgileRelative sizingTeam | AlignmentStakeholdersStrategyFacilitation | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






