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 Theory of Constraints |  Operations ALPEN Method |  Agile Sprint Retrospective |  Operations Bottleneck Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | 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 flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 2-4 h Analyse, laufend | 10-20 min daily | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-3 h |
Participantsdifferent | 3-12 | 1 | Scrum Team | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Daily Plan, Time Estimates, Review Notes | Improvement actions, Team agreements | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | OperationsConstraintsFlowImprovement | PlanningTime managementProductivityOperations | RetrospectiveImprovementLearning | FlowMeasurementConstraints |