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 for Three-Point Estimation.
Decision Making
Three-Point Estimation
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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 PERT Estimation.
Decision Making
PERT Estimation
Purposedifferent
A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.
Complexitysame
MediumMediumMediumMedium
Timedifferent
10-30 min je Item45-90 min3–4 h for initial assessment; preparation and deeper analysis additional15-45 min
Participantsdifferent
1-82-51 or a small team; particularly suitable for 3–4 people1-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Three-Point Estimate, Risk Range, Assumption NotesA3 Report, Action Plan, Root Cause AnalysisLean 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 checksPERT Estimate, Expected Value, Risk Notes
Tagsno overlap
EstimationUncertaintyForecasting
LeanProblem solvingCoachingOperations
ArchitectureQualityRiskAssessmentLean
EstimationUncertaintyRisk
Add more methods