View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Stakeholder Salience Model |  Agile ROAM Board |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min | 20-40 min initial, dann laufend |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-6 | 3-15 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Salience Diagram, Strategy per Class | ROAM Board, Owner List |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | StakeholdersFacilitationAlignmentGovernance | RiskAgileTrackingAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
