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 |
|---|---|---|---|
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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-120 min | 1-3 h |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Waste Map, Prioritized Waste, Improvement Backlog | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | AgileIterationCadence | WasteLeanProcess improvement | ProcessOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
