View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Communication Canvas |  Agile Starfish Retrospective |  Agile Start Stop Continue |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 60-120 min | 45-90 min | 30-60 min | 1-2 Tage |
Participantsdifferent | 2-8 | 4-12 | 3-12 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | ArchitectureDocumentationCommunication |