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 BoardSAAM (Software Architecture Analysis Method)RAID LogATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Agile ROAM Board |  Architecture SAAM (Software Architecture Analysis Method) |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. | 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. |
Complexitydifferent | Low | High | Low | High |
Timedifferent | 20-40 min initial, dann laufend | Preparation, scenario analysis, and findings review; effort depends on scope | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-15 | Architecture experts and stakeholders for scenarios and weighting | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | ROAM Board, Owner List | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | RAID Log, Status Report Source | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | RiskAgileTrackingAlignment | ArchitectureChangeAnalysisComparisonQuality | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders |