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 Sprint Retrospective |  Agile Starfish Retrospective |  Growth Growth Experiment |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 1-2 Wochen | 30-60 min |
Participantsdifferent | Scrum Team | 4-12 | 1-6 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Improvement actions, Team agreements | Starfish Board, Practice Changes, Experiments | Experiment card, Result summary, Next bet | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementLearning | RetrospectiveImprovementExperimentsTeam | MarketingGrowthExperimentsLearning | RetrospectiveImprovementTeamReflection |