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 a MoSCoW board with four columns and a visible release boundary.
Delivery
MoSCoW
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved.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.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitydifferent
LowLowHighMedium
Timedifferent
30-90 min30 min Setup, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
3-121-3 maintaining, briefing for everyoneEvaluation team, architects, and relevant stakeholders3-20 Reviewer
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Prioritized Backlog, Release Scope, Tradeoff NotesRAID Log, Status Report SourcePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
PrioritizationScopeDecision
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDecisionAsyncGovernance
Add more methods