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 Start Stop Continue |  Operations Process 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 | Low | Medium | Low |
Timedifferent | 45-90 min | 30-60 min | 1-3 h | 45-90 min |
Participantsdifferent | 4-12 | 3-12 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions | Process Map, Handoff List, Improvement Backlog | Starfish Board, Practice Changes, Experiments |
Tags1 shared | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection | ProcessOperationsImprovement | RetrospectiveImprovementExperimentsTeam |