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 Waste Analysis |  Agile WSJF |  Delivery MoSCoW |
|---|---|---|---|
Purposedifferent | 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. | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. |
Complexitydifferent | Low | High | Low |
Timedifferent | 45-120 min | 45-90 min | 30-90 min |
Participantsdifferent | 2-8 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Ranked Backlog, Cost-of-Delay Assumptions | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | WasteLeanProcess improvement | LeanEconomicsSequencePrioritization | PrioritizationScopeDecision |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
