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 ARID (Active Reviews for Intermediate Designs) |  Architecture Views and Beyond |  Architecture Risk Storming |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 Tage | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Designers, developers as users, and facilitation | 1-4 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Architecture Views, Cross-view Notes, Rationale | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureEngineeringFeedbackValidationTasks | DocumentationStakeholdersArchitecture | RiskArchitectureWorkshopValidation |