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 Starfish Retrospective |  Architecture Architecture Communication Canvas |  Architecture Views and Beyond |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 60-120 min | 1-3 Tage | 45–75 min |
Participantsdifferent | 4-12 | 2-8 | 1-4 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Views, Cross-view Notes, Rationale | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | ArchitectureCommunicationStakeholdersCanvas | DocumentationStakeholdersArchitecture | RetrospectiveLearningReflectionTeam |