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 of a Strategy Canvas with several value curves
Business Strategy
Blue Ocean Strategy Canvas
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 Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
The Blue Ocean Strategy Canvas shows how an offering is positioned relative to the market. Differentiation thereby becomes tangible in value factors instead of merely being claimed.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 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
MediumMediumMediumHigh
Timedifferent
2-4 h3–4 h for initial assessment; preparation and deeper analysis additional1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-101 or a small team; particularly suitable for 3–4 people4-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Strategy Canvas, Value Curve, ERRC ActionsLean 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 checksAlignment 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
StrategyPositioningInnovationValue
ArchitectureQualityRiskAssessmentLean
AlignmentStakeholdersStrategyFacilitation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods