View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RAID LogArchitecture Communication Canvas5 WhysATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Delivery RAID Log |  Architecture Architecture Communication Canvas |  Operations 5 Whys |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Low | High |
Timedifferent | 30 min Setup, dann laufend | 60-120 min | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 2-6 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Root cause notes, Countermeasures | 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 | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | Root causeIncidentLeanProblem solving | ArchitectureQualityRiskTradeoffsStakeholders |