View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |  Product Strategy RICE Scoring |
|---|---|---|---|
Purposedifferent | 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. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | 2-10 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | 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 | RICE Scores, Ranked List, Assumption Log |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance | PrioritizationScoringRoadmapTradeoffs |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
