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 Scrum |  Architecture Architecture Decision Record |  Agile ROAM Board |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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. | 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 | Medium | Low | Low | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 15-45 min | 20-40 min initial, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 | 3-15 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | ADR File, Decision Log, Rationale | ROAM Board, Owner List | 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 | AgileIterationCadence | ArchitectureRationaleDocumentationGovernance | RiskAgileTrackingAlignment | ArchitectureQualityRiskTradeoffsStakeholders |