methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.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
LowHighLowLow
Timedifferent
30-60 min90-180 min1-2 h60-90 min
Participantsdifferent
3-103-83-104-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Risk Matrix, Top Risk ListCoD Table, Prioritization SequenceArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
RiskDecisionPrioritizationAssessment
PrioritizationDeliveryEconomicsDecision
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
Add more methods