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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Paper illustration for Change Analysis.
Operations
Change Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
HighLowMediumLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope1 h bis mehrere Wochen45-120 min15-30 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders1-82-62-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeChange Matrix, Cause Hypotheses, Validation Questions, Action ListRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Continuous improvementLeanExperiments
ChangeRoot causeTroubleshootingComparison
Root causeIncidentLeanProblem solving
Add more methods