View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Assumption Surfacing |
|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | High | Low |
Timedifferent | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | 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 | Assumption List, Critical Assumptions, Learning Plan |
Tags1 shared | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskDecisionDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
