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 Risk Storming.
Architecture
Risk Storming
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
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)
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.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.A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.
Complexitydifferent
LowLowMediumMedium
Timedifferent
60-90 min20-40 min pro Story3–4 h for initial assessment; preparation and deeper analysis additional2-4 h
Participantsdifferent
4-123-61 or a small team; particularly suitable for 3–4 people5-15
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogAcceptance Criteria, Story UpdateLean 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 checksQuality Scenarios, Priority List, Architecture Concerns
Tagsno overlap
RiskArchitectureWorkshopValidation
AgileRequirementsRefinementBehavior-Driven Development
ArchitectureQualityRiskAssessmentLean
RequirementsArchitectureWorkshop
Add more methods