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 Getting Things Done |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|---|
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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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 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 | Medium | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-2 h Setup, laufend | 30-60 min | 45-90 min |
Participantsdifferent | Scrum Team | 1 | 3-12 | 4-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Improvement actions, Team agreements | Action Lists, Project List, Review Routine | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementLearning | ProductivityPlanningTasksExecution | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |