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 |  Operations After-Action Review |  Agile Starfish Retrospective |  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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 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 | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min | 45-90 min | 30-60 min |
Participantsdifferent | Scrum Team | 3-12 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Improvement actions, Team agreements | Lessons learned, Action items, Event summary | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tags1 shared | RetrospectiveImprovementLearning | LearningOperationsImprovement | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |