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 |  Decision Making Pre-Mortem |  Engineering Failure Scenario Analysis |
|---|---|---|---|
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. | 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 | Medium | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 20–45 min | 1-3 h |
Participantsdifferent | 3-10 (Scrum Team) | Small cross-functional group | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Risk list, Mitigation plan, Assumption log | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions |
Tagsno overlap | AgileIterationCadence | RiskDecisionFailurePlanning | FailureResilienceRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
