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 Start Stop Continue |  Facilitation Responsibility Poker |  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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 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 | 30-60 min | 45-90 min | 45–75 min |
Participantsdifferent | 4-12 | 3-12 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | RolesResponsibilityTeamFacilitation | RetrospectiveLearningReflectionTeam |