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 Three Amigos |  Architecture arc42 |
|---|---|---|---|---|
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-3 Tage | 15-30 min | 1-2 Tage |
Participantsdifferent | 3-7 | 1-4 | 3 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Architecture Views, Cross-view Notes, Rationale | Clarified Story, Test Examples, Open Questions | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DocumentationStakeholdersArchitecture | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureDocumentationCommunication |