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 Ivy Lee Method
Operations
Ivy Lee Method
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Eat the Frog
Operations
Eat the Frog
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.With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field.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.The method protects energy and attention for the task that creates the largest progress and is often postponed.
Complexitydifferent
MediumLowHighLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional5-10 min dailySeveral meetings plus preparation and analysis; total effort depends on scope15-90 min daily
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1Evaluation team, architects, and relevant stakeholders1
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
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 checksDaily Priority List, Completion NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPriority Task, Completion Note, Daily Focus
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
PrioritizationProductivityExecution
ArchitectureQualityRiskTradeoffsStakeholders
PrioritizationProductivityFocusExecution
Add more methods