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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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 for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
LowHighMediumHigh
Timedifferent
30 min Setup, dann laufendHalber Tag3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone5-201 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceSimulation Notes, Gaps List, Updated RunbooksLean 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 checksFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
ResilienceOperationsIncident
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods