View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ROAM BoardRequest for CommentsStakeholder Salience ModelATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Agile ROAM Board |  Architecture Request for Comments |  Facilitation Stakeholder Salience Model |  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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 | Low | Medium | Medium | High |
Timedifferent | 20-40 min initial, dann laufend | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-15 | 3-20 Reviewer | 3-6 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | ROAM Board, Owner List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Salience Diagram, Strategy per Class | Prioritized 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 | StakeholdersFacilitationAlignmentGovernance | ArchitectureQualityRiskTradeoffsStakeholders |