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 4Ls Retrospective |
|---|---|---|---|
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 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 | Medium | Low | Low |
Timedifferent | 60-120 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-8 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
