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 Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
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
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)
Purposedifferent
Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.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.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.
Complexitydifferent
HighHighMediumMedium
Timedifferent
90-180 minSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-8Evaluation team, architects, and relevant stakeholders2-101 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
CoD Table, Prioritization SequencePrioritized 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 LogLean 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 checks
Tagsno overlap
PrioritizationDeliveryEconomicsDecision
ArchitectureQualityRiskTradeoffsStakeholders
PrioritizationScoringRoadmapTradeoffs
ArchitectureQualityRiskAssessmentLean
Add more methods