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 |  Decision Making Decision Rights Mapping |  Architecture Architecture Decision Record |  Architecture Request for Comments |
|---|---|---|---|---|
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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 20-40 min initial, dann laufend | 90-180 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-15 | 4-12 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | ROAM Board, Owner List | Decision Rights Matrix, Agreement | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RiskAgileTrackingAlignment | DecisionGovernanceAlignmentResponsibility | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |