View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Sailboat RetrospectiveTeam Topologies Interaction ModesStarfish Retrospective4Ls Retrospective
| Criterion |  Agile Sailboat Retrospective |  Team Design Team Topologies Interaction Modes |  Agile Starfish Retrospective |  Agile 4Ls 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 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 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 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 | Half day | 45-90 min | 45–75 min |
Participantsdifferent | 4-12 | Team-Leads plus Architecture | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Interaction Heat Map, Agreements per Pair | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveTeamImprovement | TeamAlignmentCollaborationOrganization | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |