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 Topologies Interaction Modes |  Agile Working Agreements |  Agile Planning Poker |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Half day | 45-90 min | 2-5 min je Item | 90-180 min |
Participantsdifferent | Team-Leads plus Architecture | 3-12 | 3-9 | 5-15 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Working Agreements, Team Norms, Review Cadence | Relative Estimates, Assumption Notes, Split Candidates | Spotify Model Map, Action List |
Tags1 shared | TeamAlignmentCollaborationOrganization | TeamCollaborationAgile | EstimationAgileRelative sizingTeam | TeamOrganizationAlignmentDiagnosis |