View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Communication CanvasAcceptance Criteria WorkshopArchitecture Decision RecordExample Mapping
| Criterion |  Architecture Architecture Communication Canvas |  Agile Acceptance Criteria Workshop |  Architecture Architecture Decision Record |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-120 min | 20-40 min pro Story | 15-45 min | 30-60 min |
Participantsdifferent | 2-8 | 3-6 | 1-3 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Acceptance Criteria, Story Update | ADR File, Decision Log, Rationale | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement |