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 Architecture Communication Canvas |  Architecture Risk Storming |  Architecture Software Architecture 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 60-120 min | 60-90 min | 1-2 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 4-12 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | RiskArchitectureWorkshopValidation | CanvasArchitectureAlignmentWorkshop |