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
A paper-based illustration representing Context Canvas with its core stages and visible working result.
Product Discovery
Context 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)
Paper illustration of Design Charrette with its method-specific working model.
Innovation
Design Charrette
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Purposedifferent
When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency.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.In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space.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
LowMediumMediumMedium
Timedifferent
45-90 min3–4 h for initial assessment; preparation and deeper analysis additionalHalber Tag bis mehrere Tage2-4 h
Participantsdifferent
3-101 or a small team; particularly suitable for 3–4 people10-505-15
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Context canvas, Open questions, Shared context notesLean 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 checksSketches and Concepts, Consolidated Solution Sketch, Prioritized DirectionQuality Scenarios, Priority List, Architecture Concerns
Tagsno overlap
ContextFramingRequirementsCanvas
ArchitectureQualityRiskAssessmentLean
BrainstormingWorkshopCollaborationIdeation
RequirementsArchitectureWorkshop
Add more methods