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 Software Architecture Canvas |  Decision Making Assumption Surfacing |  Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 90-180 min | 1-2 h | 45-90 min | 60-90 min |
Participantsdifferent | 3-8 | 3-10 | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | CoD Table, Prioritization Sequence | Architecture Canvas, Goals, Constraints, Quality Attributes | Assumption List, Critical Assumptions, Learning Plan | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | CanvasArchitectureAlignmentWorkshop | AssumptionsRiskDecisionDiscovery | RiskArchitectureWorkshopValidation |