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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
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.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h20–45 min3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
3-8Small cross-functional group1 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Failure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsRisk list, Mitigation plan, Assumption logLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksRisk Matrix, Top Risk List
Tags1 shared
FailureResilienceRisk
RiskDecisionFailurePlanning
ArchitectureQualityRiskAssessmentLean
RiskDecisionPrioritizationAssessment
Add more methods