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 a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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
30-60 min1-2 h3–4 h for initial assessment; preparation and deeper analysis additional2-4 h
Participantsdifferent
3-73-101 or a small team; particularly suitable for 3–4 people5-15
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality AttributesLean 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
Behavior-Driven DevelopmentRequirementsExamplesRefinement
CanvasArchitectureAlignmentWorkshop
ArchitectureQualityRiskAssessmentLean
RequirementsArchitectureWorkshop
Add more methods