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 Acceptance Criteria Workshop |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-3 Tage | 20-40 min pro Story | 15-45 min |
Participantsdifferent | 3-7 | 1-4 | 3-6 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Architecture Views, Cross-view Notes, Rationale | Acceptance Criteria, Story Update | ADR File, Decision Log, Rationale |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DocumentationStakeholdersArchitecture | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance |