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 Scrum |  Operations After-Action Review |  Operations A3 Problem Solving |  Operations Kaizen Event |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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. | For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 20-45 min | 45-90 min | 0.5-5 Tage |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 2-5 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Lessons learned, Action items, Event summary | A3 Report, Action Plan, Root Cause Analysis | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update |
Tagsno overlap | AgileIterationCadence | LearningOperationsImprovement | LeanProblem solvingCoachingOperations | LeanContinuous improvementOperations |