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)
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional60–90 min1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-84-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + 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 checksStakeholder Map, Engagement Plan, Risk NotesAlignment Map, Open Issues, Decision QuestionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
StakeholdersAlignmentFacilitationChange
AlignmentStakeholdersStrategyFacilitation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods