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 |  Agile Specification by Example |  Domain Modeling Context Map |  Agile Three Amigos |
|---|---|---|---|---|
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. | 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. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 60-90 min pro Feature | 1-3 h | 15-30 min |
Participantsdifferent | 3-7 | 3-6 | 2-8 | 3 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Context Map, Integration Patterns, Boundary Notes | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | Domain-Driven DesignBoundariesStrategy | CollaborationBehavior-Driven DevelopmentQualityRefinement |