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