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 Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
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.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.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
HighLowLowLow
Timedifferent
90-180 min45-90 min1-2 h60-90 min
Participantsdifferent
3-82-83-104-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
CoD Table, Prioritization SequenceAssumption List, Critical Assumptions, Learning PlanArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
PrioritizationDeliveryEconomicsDecision
AssumptionsRiskDecisionDiscovery
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
Add more methods