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 LogARID (Active Reviews for Intermediate Designs)LASR (Lightweight Approach for Software Reviews)Architecture Communication Canvas
| Criterion |  Delivery RAID Log |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 2–4 h review as a planning range; preparation and evaluation additional | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Designers, developers as users, and facilitation | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskAssessmentLean | ArchitectureCommunicationStakeholdersCanvas |