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 of a six-field PESTLE grid
Business Strategy
PESTLE Analysis
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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.PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends.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.
Complexitysame
MediumMediumMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-3 h1-2 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-104-12
Formatdifferent
Workshop + asyncWorkshop + 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 checksPESTLE Map, External Risks, Strategic QuestionsAlignment Map, Open Issues, Decision Questions
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
StrategyMarketAnalysis
AlignmentStakeholdersStrategyFacilitation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Stakeholder Mapping
Facilitation
Stakeholder Mapping