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 Starfish Retrospective |  Product Discovery Experiment Canvas |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45–75 min | 45-90 min | 30-60 min | 30-60 min |
Participantsdifferent | Team members involved | 4-12 | 1-5 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments | Completed Experiment Canvas, Success Metric | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam | ExperimentsValidationDiscoveryHypothesis | RetrospectiveImprovementTeamReflection |