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 |  Operations Process Mapping |  Operations Learning Review |
|---|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 1-3 h | 1-3 h |
Participantsdifferent | Scrum Team | 2-5 | 3-10 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Improvement actions, Team agreements | A3 Report, Action Plan, Root Cause Analysis | Process Map, Handoff List, Improvement Backlog | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementLearning | LeanProblem solvingCoachingOperations | ProcessOperationsImprovement | LearningRetrospectiveIncidentOperations |