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 Architecture Communication Canvas |  Agile Start Stop Continue |  Architecture arc42 |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 60-120 min | 30-60 min | 1-2 Tage |
Participantsdifferent | 4-12 | 2-8 | 3-12 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Start Stop Continue Board, Improvement Actions | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | RetrospectiveTeamImprovement | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementTeamReflection | ArchitectureDocumentationCommunication |