View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingViews and BeyondArchitecture Decision RecordArchitecture Communication Canvas
| Criterion |  Agile Example Mapping |  Architecture Views and Beyond |  Architecture Architecture Decision Record |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30-60 min | 1-3 Tage | 15-45 min | 60-120 min |
Participantsdifferent | 3-7 | 1-4 | 1-3 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |