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 4Ls Retrospective |  Agile Start Stop Continue |  Growth Growth Experiment |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment. | 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–75 min | 30-60 min | 1-2 Wochen | 45-90 min |
Participantsdifferent | Team members involved | 3-12 | 1-6 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Experiment card, Result summary, Next bet | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | MarketingGrowthExperimentsLearning | RetrospectiveImprovementExperimentsTeam |