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