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 Start Stop Continue |  Agile Starfish Retrospective |  Operations After-Action Review |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 45-90 min | 20-45 min | 45-90 min |
Participantsdifferent | 3-12 | 4-12 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Lessons learned, Action items, Event summary | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | LearningOperationsImprovement | RetrospectiveTeamImprovement |