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 Starfish Retrospective |  Knowledge Modeling Feynman Technique |  Agile Start Stop Continue |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 20-60 min | 30-60 min | 45–75 min |
Participantsdifferent | 4-12 | 1 | 3-12 | Team members involved |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Plain-language Explanation, Knowledge Gaps, Study Notes | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | LearningKnowledgeUnderstanding | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |