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 for Bucket System.
Agile
Bucket System
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
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 a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.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 tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional30-90 minSeveral meetings plus preparation and analysis; total effort depends on scope30-90 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people3-12Evaluation team, architects, and relevant stakeholders3-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
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 checksBucketed Backlog, Relative Estimates, Split CandidatesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
EstimationBacklogRelative sizing
ArchitectureQualityRiskTradeoffsStakeholders
EstimationBacklogRelative sizing
Add more methods