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 API |  Team Design Spotify Model Mapping |  Agile Starfish Retrospective |
|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 90-180 min | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 5-15 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Spotify Model Map, Action List | Starfish Board, Practice Changes, Experiments |
Tags1 shared | TeamAlignmentCommunicationService | TeamOrganizationAlignmentDiagnosis | RetrospectiveImprovementExperimentsTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
