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 Sprint Retrospective |  Team Design Team Cognitive Load Assessment |  Agile 4Ls Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. | 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 60-90 min | 45–75 min | 45-90 min |
Participantsdifferent | Scrum Team | 3-12 | Team members involved | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Improvement actions, Team agreements | Cognitive Load Profile, Action List | 4Ls Board, Learning Themes, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementLearning | TeamComplexityImprovementDiagnosis | RetrospectiveLearningReflectionTeam | RetrospectiveTeamImprovement |