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 Views and Beyond | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 20-40 min initial, dann laufend | 30 min Setup, dann laufend | 1-3 Tage | 1-2 h |
Participantsdifferent | 3-15 | 1-3 maintaining, briefing for everyone | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | ROAM Board, Owner List | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | AlignmentStakeholdersStrategyFacilitation |



