View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ROAM BoardARID (Active Reviews for Intermediate Designs)ATAM (Architecture Tradeoff Analysis Method)RAID Log
| Criterion |  Agile ROAM Board |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 20-40 min initial, dann laufend | 2–4 h review as a planning range; preparation and evaluation additional | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend |
Participantsdifferent | 3-15 | Designers, developers as users, and facilitation | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | ROAM Board, Owner List | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source |
Tagsno overlap | RiskAgileTrackingAlignment | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance |