View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Agile Starfish Retrospective |  Agile Sprint Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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 | 1-2 Tage | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min |
Participantsdifferent | 1-4 | 4-12 | Scrum Team | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Starfish Board, Practice Changes, Experiments | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ArchitectureDocumentationCommunication | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam |