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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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 of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.
Complexitydifferent
LowMediumLowLow
Timedifferent
15-45 min3–4 h for initial assessment; preparation and deeper analysis additional20-40 min pro Story30-60 min
Participantsdifferent
1-31 or a small team; particularly suitable for 3–4 people3-63-7
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, RationaleLean 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 checksAcceptance Criteria, Story UpdateExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskAssessmentLean
AgileRequirementsRefinementBehavior-Driven Development
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods