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 Domain Context Map |  Agile Sailboat Retrospective |  Domain Modeling Bounded Context Canvas |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 3-10 | 4-12 | 3-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Sailboat Board, Risks, Improvement Actions | Context Canvas, Glossary, Integration Notes | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | Domain-Driven DesignContextBoundaries | RetrospectiveTeamImprovement | Domain-Driven DesignBoundariesModeling | RetrospectiveImprovementExperimentsTeam |