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 Domain Context Map |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
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 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 20-40 min pro Story |
Participantsdifferent | 3-6 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Domain Context Map, Boundary Notes, Ownership Map | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Domain-Driven DesignContextBoundaries | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
