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 for Risk Storming.
Architecture
Risk Storming
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowMediumLowLow
Timedifferent
60-90 min1-2 h Setup, laufend1-2 h1-2 h
Participantsdifferent
4-1213-103-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogAction Lists, Project List, Review RoutineArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
RiskArchitectureWorkshopValidation
ProductivityPlanningTasksExecution
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods