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 |  Operations A3 Problem Solving |  Agile 4Ls 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 45–75 min |
Participantsdifferent | Scrum Team | 2-5 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Improvement actions, Team agreements | A3 Report, Action Plan, Root Cause Analysis | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementLearning | LeanProblem solvingCoachingOperations | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
