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 |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 15-45 min |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | 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 | ADR File, Decision Log, Rationale |
Tagsno overlap | AgileIterationCadence | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureRationaleDocumentationGovernance |