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 Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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 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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
MediumLowHighHigh
Timedifferent
Wochen bis Monate je Lernzyklus30 min Setup, dann laufend1-4 WochenSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-81-3 maintaining, briefing for everyone1-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Hypothesis list, MVPs, Learning reports, Pivot or persevere decisionRAID Log, Status Report SourceExperiment results, Decision log, Learning summaryPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
LeanStartupValidationMVP
RiskTrackingStakeholdersGovernance
ExperimentsGrowthAnalyticsValidation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods