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 Starfish Retrospective |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|
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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 45-90 min | 1-3 h |
Participantsdifferent | 2-8 | 4-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Starfish Board, Practice Changes, Experiments | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | RetrospectiveImprovementExperimentsTeam | Domain-Driven DesignBoundariesModeling |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
