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 yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.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.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.
Complexitysame
LowLowLowLow
Timedifferent
30-60 min1-2 h60-90 min1-2 h
Participantsdifferent
3-73-104-123-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action BacklogInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
AlignmentArchitectureCanvas
Add more methods