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
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.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 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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30 min Setup, dann laufend2-4 h3–4 h for initial assessment; preparation and deeper analysis additional15-30 min
Participantsdifferent
1-3 maintaining, briefing for everyone2-61 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceBarrier Inventory, Failure Analysis per Barrier, Action BacklogLean 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 checksRoot cause notes, Countermeasures
Tagsno overlap
RiskTrackingStakeholdersGovernance
Root causeSafetyIncident
ArchitectureQualityRiskAssessmentLean
Root causeIncidentLeanProblem solving
Add more methods