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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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)
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Purposedifferent
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.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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.
Complexitydifferent
HighMediumHighHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope3–4 h for initial assessment; preparation and deeper analysis additional45-90 min90-180 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders1 or a small team; particularly suitable for 3–4 people3-103-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsLean 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 checksRanked Backlog, Cost-of-Delay AssumptionsCoD Table, Prioritization Sequence
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureQualityRiskAssessmentLean
LeanEconomicsSequencePrioritization
PrioritizationDeliveryEconomicsDecision
Add more methods