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 Start Stop Continue | ![]() Agile Sailboat 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 | 3-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | Domain-Driven DesignContextBoundaries | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






