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 |  Operations ALPEN Method |  Agile Starfish Retrospective |  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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | 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 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 | 30-60 min | 10-20 min daily | 45-90 min | 45–75 min |
Participantsdifferent | 3-12 | 1 | 4-12 | Team members involved |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Daily Plan, Time Estimates, Review Notes | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | PlanningTime managementProductivityOperations | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |