View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordAffinity EstimationATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture Architecture Decision Record |  Agile Affinity Estimation |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | 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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. | 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 | Medium | High |
Timedifferent | 15-45 min | 30-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-3 | 3-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Affinity Size Map, Grouped Estimates, Unclear Items | 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 | ArchitectureRationaleDocumentationGovernance | EstimationBacklogRelative sizing | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
