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 Software Architecture Canvas |  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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Low | Medium |
Timedifferent | 20-40 min initial, dann laufend | 1-2 h | 60-90 min |
Participantsdifferent | 3-15 | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | ROAM Board, Owner List | Architecture Canvas, Goals, Constraints, Quality Attributes | Salience Diagram, Strategy per Class |
Tags1 shared | RiskAgileTrackingAlignment | CanvasArchitectureAlignmentWorkshop | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
