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 Standard Work Analysis.
Operations
Standard Work Analysis
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitysame
MediumMediumMediumMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-3 h1-3 h1-3 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-63-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + 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 checksStandard Work Sheet, Deviation List, Improved Standard, Training NeedsDomain Context Map, Boundary Notes, Ownership MapContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
LeanProcessQuality
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesStrategy
Add more methods