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 ICE Scoring with its method-specific working model.
Product Strategy
ICE Scoring
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a scoring table with four factor columns, a calculator and three ordered initiative cards.
Product Strategy
RICE Scoring
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 ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable.
Complexitydifferent
MediumLowHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-8Evaluation team, architects, and relevant stakeholders2-10
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 checksICE Table, Top Idea ListPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRICE Scores, Ranked List, Assumption Log
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
PrioritizationScoringGrowthDecision
ArchitectureQualityRiskTradeoffsStakeholders
PrioritizationScoringRoadmapTradeoffs
Add more methods