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 Architecture Decision Record |  Agile Sprint Retrospective |  Architecture C4 Model |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-4 h | 60-120 min |
Participantsdifferent | 1-3 | Scrum Team | 1-5 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Improvement actions, Team agreements | Context Diagram, Container Diagram, Component Diagram | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementLearning | ArchitectureCommunicationVisualization | ArchitectureCommunicationStakeholdersCanvas |