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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.
Complexitydifferent
MediumMediumLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional3–4 h for initial assessment; preparation and deeper analysis additional20-40 min pro Story
Participantsdifferent
Designers, developers as users, and facilitation1 or a small team; particularly suitable for 3–4 people3-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsLean 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 Update
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskAssessmentLean
AgileRequirementsRefinementBehavior-Driven Development
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 of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example