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 |  Agile Sailboat Retrospective |  Operations Learning Review |  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 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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 | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | 1-3 h | 45–75 min |
Participantsdifferent | 4-12 | 4-12 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations | RetrospectiveLearningReflectionTeam |