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
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 Risk Storming.
Architecture
Risk Storming
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.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
MediumLowLowLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional60-90 min30-60 min15-30 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people4-122-82-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Lean 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 checksAnnotated Diagram, Prioritized Risk List, Action BacklogFishbone Diagram, Cause Categories, Investigation BacklogRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
RiskArchitectureWorkshopValidation
Root causeQualityOperations
Root causeIncidentLeanProblem solving
Add more methods