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 Scatter Diagram with its method-specific working model.
Operations
Scatter Diagram
Paper illustration for Pareto Analysis
Decision Making
Pareto 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
When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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
LowLowMediumLow
Timedifferent
30-90 min30-60 min3–4 h for initial assessment; preparation and deeper analysis additional15-30 min
Participantsdifferent
1-41-61 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Scatter Plot, Korrelationsnotiz, HypothesenlistePareto Chart, Top Causes, Focus ListLean 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
Root causeQualityVisualization
PrioritizationQualityFocusRoot cause
ArchitectureQualityRiskAssessmentLean
Root causeIncidentLeanProblem solving
Add more methods