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 |  Delivery RAID Log |  Architecture arc42 |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | Medium |
Timedifferent | 20-40 min initial, dann laufend | 30 min Setup, dann laufend | 1-2 Tage | 60-90 min |
Participantsdifferent | 3-15 | 1-3 maintaining, briefing for everyone | 1-4 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | ROAM Board, Owner List | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance |