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 Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration of a MoSCoW board with four columns and a visible release boundary.
Delivery
MoSCoW
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.Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures.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 a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved.
Complexitydifferent
MediumMediumLowLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional2-4 h30-60 min30-90 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-83-103-12
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 checksCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixRisk Matrix, Top Risk ListPrioritized Backlog, Release Scope, Tradeoff Notes
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
OntologyKnowledge graphScopeRequirementsSemantic
RiskDecisionPrioritizationAssessment
PrioritizationScopeDecision
Add more methods