View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Communication CanvasSailboat Retrospective4Ls RetrospectiveSprint Retrospective
| Criterion |  Architecture Architecture Communication Canvas |  Agile Sailboat Retrospective |  Agile 4Ls Retrospective |  Agile Sprint 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 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 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-120 min | 45-90 min | 45–75 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 2-8 | 4-12 | Team members involved | Scrum Team |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementLearning |