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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
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 DMAIC.
Operations
DMAIC
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.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.
Complexitydifferent
LowMediumHigh
Timedifferent
1-2 h3–4 h for initial assessment; preparation and deeper analysis additional2-12 Wochen
Participantsdifferent
2-81 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeLean 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 checksProject Charter, Measurement Plan, Cause Analysis, Control Plan
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ArchitectureQualityRiskAssessmentLean
Continuous improvementQualityProcess improvement
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 for Standard Work Analysis.
Operations
Standard Work Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk