View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Agile Specification by Example |  Decision Making Pre-Mortem |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 60-90 min pro Feature | 20–45 min | 45-90 min |
Participantsdifferent | 3-8 | 3-6 | Small cross-functional group | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Example Table, Acceptance Tests | Risk list, Mitigation plan, Assumption log | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | FailureResilienceRisk | AgileRequirementsExamplesBehavior-Driven Development | RiskDecisionFailurePlanning | AssumptionsRiskDecisionDiscovery |