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 |  Architecture arc42 |  Architecture Architecture Decision Record |  Agile Start Stop Continue |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 1-2 Tage | 15-45 min | 30-60 min |
Participantsdifferent | 4-12 | 1-4 | 1-3 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementTeamReflection |