View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:4Ls RetrospectiveArchitecture Decision RecordArchitecture Communication CanvasViews and Beyond
| Criterion | ![]() Agile 4Ls Retrospective | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas | ![]() Architecture Views and Beyond |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45–75 min | 15-45 min | 60-120 min | 1-3 Tage |
Participantsdifferent | Team members involved | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | RetrospectiveLearningReflectionTeam | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas | DocumentationStakeholdersArchitecture |



