View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling PARA Method |  Agile Starfish Retrospective |  Architecture arc42 |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 45-90 min | 1-2 Tage | 45–75 min |
Participantsdifferent | 1 | 4-12 | 1-4 | Team members involved |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Starfish Board, Practice Changes, Experiments | Architecture Document, Context View, Runtime View, Deployment View | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | KnowledgeProductivityOrganization | RetrospectiveImprovementExperimentsTeam | ArchitectureDocumentationCommunication | RetrospectiveLearningReflectionTeam |