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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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 an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.
Complexitydifferent
LowLowMediumMedium
Timedifferent
60-90 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional1-2 Wochen pro Iteration
Participantsdifferent
4-122-81 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogAssumption List, Critical Assumptions, Learning PlanLean 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 checksPrioritized Assumption List, Test Plan, Results Report
Tagsno overlap
RiskArchitectureWorkshopValidation
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskAssessmentLean
ExperimentsValidationDiscoveryAssumptions
Add more methods