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 Waste Analysis |  Operations Process Mapping |  Operations After-Action Review |
|---|---|---|---|---|
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. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-120 min | 1-3 h | 20-45 min |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Waste Map, Prioritized Waste, Improvement Backlog | Process Map, Handoff List, Improvement Backlog | Lessons learned, Action items, Event summary |
Tagsno overlap | AgileIterationCadence | WasteLeanProcess improvement | ProcessOperationsImprovement | LearningOperationsImprovement |