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 Learning Review |  Agile 4Ls 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 a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-60 min | 45-90 min | 1-3 h | 45–75 min |
Participantsdifferent | 3-12 | 4-12 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Learning Review Notes, System Factors, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | LearningRetrospectiveIncidentOperations | RetrospectiveLearningReflectionTeam |