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