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 |  Facilitation Responsibility Poker |  Agile Starfish Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 4-12 | 3-10 | 4-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tags1 shared | RetrospectiveTeamImprovement | RolesResponsibilityTeamFacilitation | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |