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 Cost of Delay |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture arc42 |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 90-180 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 Tage | 45-90 min |
Participantsdifferent | 3-8 | Designers, developers as users, and facilitation | 1-4 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Architecture Document, Context View, Runtime View, Deployment View | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureDocumentationCommunication | CommunicationStakeholdersDeliveryPlanning |