View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:4Ls RetrospectiveArchitecture Communication CanvasSailboat RetrospectiveStarfish Retrospective
| Criterion |  Agile 4Ls Retrospective |  Architecture Architecture Communication Canvas |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45–75 min | 60-120 min | 45-90 min | 45-90 min |
Participantsdifferent | Team members involved | 2-8 | 4-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveLearningReflectionTeam | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |