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 WSJF |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery Cost of Delay |
|---|---|---|---|---|
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 1-3 h | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 90-180 min |
Participantsdifferent | 3-8 | 3-10 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Ranked Backlog, Cost-of-Delay Assumptions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | CoD Table, Prioritization Sequence |
Tagsno overlap | FailureResilienceRisk | LeanEconomicsSequencePrioritization | ArchitectureQualityRiskTradeoffsStakeholders | PrioritizationDeliveryEconomicsDecision |