View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery MoSCoW |  Decision Making Pre-Mortem |  Engineering Failure Scenario Analysis |
|---|---|---|---|
Purposedifferent | 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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-90 min | 20–45 min | 1-3 h |
Participantsdifferent | 3-12 | Small cross-functional group | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | Risk list, Mitigation plan, Assumption log | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions |
Tagsno overlap | PrioritizationScopeDecision | RiskDecisionFailurePlanning | FailureResilienceRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
