View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  Operations After-Action Review |  Operations Theory of Constraints |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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 system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 30-60 min | 20-45 min | 2-4 h Analyse, laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 1-5 | 3-12 | 3-12 | Scrum Team |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ABC Classification, Focus Rules, Control List | Lessons learned, Action items, Event summary | Constraint Map, Improvement Plan, Flow Metrics | Improvement actions, Team agreements |
Tagsno overlap | PrioritizationOperationsPortfolio | LearningOperationsImprovement | OperationsConstraintsFlowImprovement | RetrospectiveImprovementLearning |