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 |  Facilitation Expectation Mapping |  Architecture Software Architecture Canvas |  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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 1-2 h | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Expectation Map, Alignment Notes, Agreements | Architecture Canvas, Goals, Constraints, Quality Attributes | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersTeam | CanvasArchitectureAlignmentWorkshop | RiskArchitectureWorkshopValidation |