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 arc42 |  Agile 4Ls Retrospective |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 1-2 Tage | 45–75 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 4-12 | 1-4 | Team members involved | Scrum Team |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Architecture Document, Context View, Runtime View, Deployment View | 4Ls Board, Learning Themes, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveTeamImprovement | ArchitectureDocumentationCommunication | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementLearning |