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 |  Agile Starfish 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 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-60 min | 45-90 min | 1-3 h |
Participantsdifferent | 3-12 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | Domain-Driven DesignBoundariesStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
