Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Failure Scenario Analysis ATAM (Architecture Tradeoff Analysis Method)Game Day Fishbone Diagram

Criterion	Engineering Failure Scenario Analysis	Architecture ATAM (Architecture Tradeoff Analysis Method)	DevOps Game Day	Operations Fishbone Diagram
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.	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.	In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.	When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent	Medium	High	High	Low
Timedifferent	1-3 h	Several meetings plus preparation and analysis; total effort depends on scope	Halber Tag	30-60 min
Participantsdifferent	3-8	Evaluation team, architects, and relevant stakeholders	5-20	2-8
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Simulation Notes, Gaps List, Updated Runbooks	Fishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap	FailureResilienceRisk	ArchitectureQualityRiskTradeoffsStakeholders	ResilienceOperationsIncident	Root causeQualityOperations

Add more methods