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 Start Stop Continue |  Domain Modeling Bounded Context Canvas |  Agile Sailboat Retrospective |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30-60 min | 1-3 h | 45-90 min | 1-3 h |
Participantsdifferent | 3-12 | 3-8 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Context Canvas, Glossary, Integration Notes | Sailboat Board, Risks, Improvement Actions | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | RetrospectiveImprovementTeamReflection | Domain-Driven DesignBoundariesModeling | RetrospectiveTeamImprovement | Domain-Driven DesignBoundariesStrategy |