View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Example Mapping | ![]() Architecture Views and Beyond | ![]() Agile Specification by Example | ![]() 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Medium | Medium |
Timedifferent | 30-60 min | 1-3 Tage | 60-90 min pro Feature | 60-120 min |
Participantsdifferent | 3-7 | 1-4 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Architecture Views, Cross-view Notes, Rationale | Example Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DocumentationStakeholdersArchitecture | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas |



