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 |  Agile Starfish Retrospective |  Operations Accountability Ladder |  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 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. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 20-45 min | 45–75 min |
Participantsdifferent | 4-12 | 4-12 | 1-8 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Ownership Reflection, Action Commitment, Coaching Notes | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | ResponsibilityLeadershipTeam | RetrospectiveLearningReflectionTeam |