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 of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional45-60 min30-60 min1-2 Wochen pro Iteration
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-83-102-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
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 checksAssumption map, Test backlog, Risk rankingRisk Matrix, Top Risk ListPrioritized Assumption List, Test Plan, Results Report
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
AssumptionsRiskExperimentsValidation
RiskDecisionPrioritizationAssessment
ExperimentsValidationDiscoveryAssumptions
Add more methods