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 ABC Analysis |  Delivery RAID Log |  Operations A3 Problem Solving |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | Low | Medium | High |
Timedifferent | 30-60 min | 30 min Setup, dann laufend | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-5 | 1-3 maintaining, briefing for everyone | 2-5 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | RAID Log, Status Report Source | A3 Report, Action Plan, Root Cause Analysis | 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 | PrioritizationOperationsPortfolio | RiskTrackingStakeholdersGovernance | LeanProblem solvingCoachingOperations | ArchitectureQualityRiskTradeoffsStakeholders |