View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Scatter Diagram |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Low | High | High |
Timedifferent | 30-90 min | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 1-6 Wochen |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders | 4-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 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 | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Root causeQualityVisualization | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders | QualityProblem solvingRoot cause |