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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
LowMediumMediumHigh
Timedifferent
20-40 min initial, dann laufend1-3 Wochen vom Draft bis zur Entscheidung1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-153-20 Reviewer4-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
ROAM Board, Owner ListRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsAlignment Map, Open Issues, Decision QuestionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskAgileTrackingAlignment
ArchitectureDecisionAsyncGovernance
AlignmentStakeholdersStrategyFacilitation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods