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) |  Operations Getting Things Done |  Operations Fishbone Diagram |
|---|---|---|---|
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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h Setup, laufend | 30-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Action Lists, Project List, Review Routine | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ProductivityPlanningTasksExecution | Root causeQualityOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
