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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.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
LowLowLowHigh
Timedifferent
15-45 min30 min Setup, dann laufend20-40 min pro StorySeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-31-3 maintaining, briefing for everyone3-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncAsyncWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleRAID Log, Status Report SourceAcceptance Criteria, Story UpdatePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RiskTrackingStakeholdersGovernance
AgileRequirementsRefinementBehavior-Driven Development
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods