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 ALPEN Method
Operations
ALPEN Method
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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 an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.
Complexitydifferent
MediumLowHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional10-20 min dailyPreparation, scenario analysis, and findings review; effort depends on scope45-90 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1Architecture experts and stakeholders for scenarios and weighting2-5
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + 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 checksDaily Plan, Time Estimates, Review NotesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesA3 Report, Action Plan, Root Cause Analysis
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
PlanningTime managementProductivityOperations
ArchitectureChangeAnalysisComparisonQuality
LeanProblem solvingCoachingOperations
Add more methods