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 Specification by Example |  Domain Modeling Bounded Context Canvas |  Agile Three Amigos |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
Purposedifferent | 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 a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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 | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 1-3 h | 15-30 min | 1-3 h |
Participantsdifferent | 3-6 | 3-8 | 3 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Context Canvas, Glossary, Integration Notes | Clarified Story, Test Examples, Open Questions | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Domain-Driven DesignBoundariesModeling | CollaborationBehavior-Driven DevelopmentQualityRefinement | Domain-Driven DesignContextBoundaries |