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 Sailboat Retrospective |  Facilitation Team Charter |  Team Design Spotify Model Mapping |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 | Medium | Low |
Timedifferent | 45-90 min | 2-4 h | 90-180 min | 45-90 min |
Participantsdifferent | 4-12 | 3-12 | 5-15 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Team Charter, Working Norms, Role Notes | Spotify Model Map, Action List | Starfish Board, Practice Changes, Experiments |
Tags1 shared | RetrospectiveTeamImprovement | TeamAlignmentCollaboration | TeamOrganizationAlignmentDiagnosis | RetrospectiveImprovementExperimentsTeam |