View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Agile Example Mapping |  Agile Three Amigos |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. | 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. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 30-60 min | 15-30 min | 1-3 h |
Participantsdifferent | 2-8 | 3-7 | 3 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | Domain-Driven DesignContextBoundaries |