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 Sprint Retrospective |  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 a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | Medium |
Timedifferent | Half day | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 90-180 min |
Participantsdifferent | Team-Leads plus Architecture | Scrum Team | 5-15 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Improvement actions, Team agreements | Spotify Model Map, Action List |
Tagsno overlap | TeamAlignmentCollaborationOrganization | RetrospectiveImprovementLearning | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
