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 Scrum |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | Half day | 90-180 min | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | Team-Leads plus Architecture | 5-15 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | AgileIterationCadence | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |