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 Three Amigos |  Architecture arc42 |  Architecture C4 Model |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-30 min | 1-2 Tage | 1-4 h | 30-60 min |
Participantsdifferent | 3 | 1-4 | 1-5 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization | Behavior-Driven DevelopmentRequirementsExamplesRefinement |