methodatlas
Compare

View methods side by side.

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

Criterion
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.
Complexitydifferent
MediumLowLowHigh
Timedifferent
1-3 h30 min Setup, dann laufend15-30 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-81-3 maintaining, briefing for everyone2-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Failure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsRAID Log, Status Report SourceRoot cause notes, CountermeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
FailureResilienceRisk
RiskTrackingStakeholdersGovernance
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods