View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Software Architecture Canvas |  Delivery RAID Log |  Architecture Risk Storming |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 60-90 min | 60-90 min |
Participantsdifferent | 3-10 | 1-3 maintaining, briefing for everyone | 4-12 | 3-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | Salience Diagram, Strategy per Class |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | StakeholdersFacilitationAlignmentGovernance |