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 Sailboat Retrospective |  Architecture Architecture Communication Canvas |  Agile Sprint Retrospective |
|---|---|---|---|
Purposedifferent | 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. | 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 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 | Low | Medium | Low |
Timedifferent | 45-90 min | 60-120 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 4-12 | 2-8 | Scrum Team |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveTeamImprovement | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
