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 for DMAIC.
Operations
DMAIC
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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)
Purposedifferent
For a process problem with fluctuating performance, the method brings analysis and improvement into a disciplined sequence. It creates a framework in which numbers, causes, and control come together.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.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.
Complexitydifferent
HighLowMediumMedium
Timedifferent
2-12 Wochen1-2 Tage45-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-101-42-51 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Project Charter, Measurement Plan, Cause Analysis, Control PlanArchitecture Document, Context View, Runtime View, Deployment ViewA3 Report, Action Plan, Root Cause AnalysisLean 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 checks
Tagsno overlap
Continuous improvementQualityProcess improvement
ArchitectureDocumentationCommunication
LeanProblem solvingCoachingOperations
ArchitectureQualityRiskAssessmentLean
Add more methods