View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making PERT Estimation |  Architecture Architecture Decision Record |  Architecture Risk Storming |  Architecture Quality Attribute Workshop |
|---|---|---|---|---|
Purposedifferent | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 15-45 min | 15-45 min | 60-90 min | 2-4 h |
Participantsdifferent | 1-8 | 1-3 | 4-12 | 5-15 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | PERT Estimate, Expected Value, Risk Notes | ADR File, Decision Log, Rationale | Annotated Diagram, Prioritized Risk List, Action Backlog | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | EstimationUncertaintyRisk | ArchitectureRationaleDocumentationGovernance | RiskArchitectureWorkshopValidation | RequirementsArchitectureWorkshop |