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 Context Map |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 60–90 min |
Participantsdifferent | 3-6 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Context Map, Integration Patterns, Boundary Notes | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Domain-Driven DesignBoundariesStrategy | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
