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 Starfish Retrospective |  Domain Modeling Context Map |  Agile Start Stop Continue |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-3 h | 30-60 min | 1-3 h |
Participantsdifferent | 4-12 | 2-8 | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Context Map, Integration Patterns, Boundary Notes | Start Stop Continue Board, Improvement Actions | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | Domain-Driven DesignBoundariesStrategy | RetrospectiveImprovementTeamReflection | Domain-Driven DesignBoundariesModeling |