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 Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.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.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.
Complexitydifferent
LowMediumLowHigh
Timedifferent
30-60 minWochen bis Monate je Lernzyklus60-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-62-84-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Pareto Chart, Top Causes, Focus ListHypothesis list, MVPs, Learning reports, Pivot or persevere decisionAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
PrioritizationQualityFocusRoot cause
LeanStartupValidationMVP
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods