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 Views and Beyond |  Agile Start Stop Continue |  Agile Starfish Retrospective |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 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. | 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 | 1-3 Tage | 30-60 min | 45-90 min | 1-2 Tage |
Participantsdifferent | 1-4 | 3-12 | 4-12 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | DocumentationStakeholdersArchitecture | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | ArchitectureDocumentationCommunication |