View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Architecture Views and Beyond | ![]() Decision Making PERT Estimation | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 Tage | 15-45 min | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | 1-8 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | PERT Estimate, Expected Value, Risk Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | EstimationUncertaintyRisk | ArchitectureRationaleDocumentationGovernance |



