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 Spotify Model Mapping |  Agile 4Ls Retrospective |  Agile Starfish Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 90-180 min | 45–75 min | 45-90 min | 30-60 min |
Participantsdifferent | 5-15 | Team members involved | 4-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tags1 shared | TeamOrganizationAlignmentDiagnosis | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |