View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Start Stop ContinueArchitecture Decision RecordSailboat RetrospectiveStarfish Retrospective
| Criterion |  Agile Start Stop Continue |  Architecture Architecture Decision Record |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 15-45 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 1-3 | 4-12 | 4-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | ADR File, Decision Log, Rationale | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementTeamReflection | ArchitectureRationaleDocumentationGovernance | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |