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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30 min Setup, dann laufend2-4 h45-60 min60-90 min
Participantsdifferent
1-3 maintaining, briefing for everyone5-152-84-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceQuality Scenarios, Priority List, Architecture ConcernsAssumption map, Test backlog, Risk rankingAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
RiskTrackingStakeholdersGovernance
RequirementsArchitectureWorkshop
AssumptionsRiskExperimentsValidation
RiskArchitectureWorkshopValidation
Add more methods