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 |  Agile ROAM Board |  Decision Making Pre-Mortem |
|---|---|---|---|---|
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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 60-90 min pro Feature | 20-40 min initial, dann laufend | 20–45 min |
Participantsdifferent | 3-8 | 3-6 | 3-15 | Small cross-functional group |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Example Table, Acceptance Tests | ROAM Board, Owner List | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | FailureResilienceRisk | AgileRequirementsExamplesBehavior-Driven Development | RiskAgileTrackingAlignment | RiskDecisionFailurePlanning |