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 the Consensus Workshop working structure.
Facilitation
Consensus 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)
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Purposedifferent
When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
MediumMediumLow
Timedifferent
1-3 h3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
5-301 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Consensus Clusters, Theme Titles, Priority AreasLean 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 checksFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
FacilitationConsensusWorkshopAlignment
ArchitectureQualityRiskAssessmentLean
Root causeQualityOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas