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 |  Knowledge Modeling PARA Method |  Agile Starfish Retrospective |  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. | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45–75 min | 1-3 h Setup, laufend | 45-90 min | 30-60 min |
Participantsdifferent | Team members involved | 1 | 4-12 | 3-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | PARA Structure, Project Notes, Knowledge Archive | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | KnowledgeProductivityOrganization | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |