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 |  Domain Modeling Bounded Context Canvas |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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 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. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 h | 45-90 min | 45–75 min |
Participantsdifferent | 2-8 | 3-8 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Context Canvas, Glossary, Integration Notes | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignBoundariesModeling | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |