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 Team Topologies Interaction Modes |  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 teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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 | Half day | 90-180 min |
Participantsdifferent | 3-9 | Team-Leads plus Architecture | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List |
Tags1 shared | EstimationAgileRelative sizingTeam | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
