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 Starfish Retrospective |  Team Design Spotify Model Mapping |  Agile Sailboat Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 90-180 min | 45-90 min | 45–75 min |
Participantsdifferent | 4-12 | 5-15 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Spotify Model Map, Action List | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | TeamOrganizationAlignmentDiagnosis | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam |