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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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
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.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 min Setup, dann laufendWochen bis Monate je Lernzyklus60-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-3 maintaining, briefing for everyone2-84-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceHypothesis 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
RiskTrackingStakeholdersGovernance
LeanStartupValidationMVP
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods