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 |  Knowledge Modeling Feynman Technique |  Agile 4Ls Retrospective |  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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-60 min | 45–75 min | 45-90 min |
Participantsdifferent | Scrum Team | 1 | Team members involved | 4-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Improvement actions, Team agreements | Plain-language Explanation, Knowledge Gaps, Study Notes | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementLearning | LearningKnowledgeUnderstanding | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam |