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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Team Topologies Interaction Modes with its method-specific working model.
Team Design
Team Topologies Interaction Modes
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.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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.
Complexitydifferent
MediumHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalSeveral meetings plus preparation and analysis; total effort depends on scopeHalf day
Participantsdifferent
1 or a small team; particularly suitable for 3–4 peopleEvaluation team, architects, and relevant stakeholdersTeam-Leads plus Architecture
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 checksPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsInteraction Heat Map, Agreements per Pair
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ArchitectureQualityRiskTradeoffsStakeholders
TeamAlignmentCollaborationOrganization
Add more methods

Often compared together

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

Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration for Team Charter.
Facilitation
Team Charter
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping