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 |  Architecture Architecture Decision Record |  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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | 15-45 min | 45–75 min |
Participantsdifferent | 1-4 | 4-12 | 1-3 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Starfish Board, Practice Changes, Experiments | ADR File, Decision Log, Rationale | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ArchitectureDocumentationCommunication | RetrospectiveImprovementExperimentsTeam | ArchitectureRationaleDocumentationGovernance | RetrospectiveLearningReflectionTeam |