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 BoardARID (Active Reviews for Intermediate Designs)Stakeholder Salience ModelATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Agile ROAM Board |  Architecture ARID (Active Reviews for Intermediate Designs) |  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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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 | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-15 | Designers, developers as users, and facilitation | 3-6 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ROAM Board, Owner List | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | 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 | ArchitectureEngineeringFeedbackValidationTasks | StakeholdersFacilitationAlignmentGovernance | ArchitectureQualityRiskTradeoffsStakeholders |