View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Sailboat RetrospectiveArchitecture Communication CanvasSprint RetrospectiveAfter-Action Review
| Criterion |  Agile Sailboat Retrospective |  Architecture Architecture Communication Canvas |  Agile Sprint Retrospective |  Operations After-Action Review |
|---|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 60-120 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 4-12 | 2-8 | Scrum Team | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveTeamImprovement | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveImprovementLearning | LearningOperationsImprovement |