View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile ROAM Board |  Architecture ARID (Active Reviews for Intermediate Designs) |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 20-40 min initial, dann laufend | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min |
Participantsdifferent | 3-15 | Designers, developers as users, and facilitation | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
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 |
Tagsno overlap | RiskAgileTrackingAlignment | ArchitectureEngineeringFeedbackValidationTasks | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
