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 Scrum with its method-specific working model.
Agile
Scrum
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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
Purposedifferent
When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-4 Wochen je Sprint, laufend1-2 h30-60 min1-2 h
Participantsdifferent
3-10 (Scrum Team)3-83-73-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalInception Canvas, Risks, Goal List, Open QuestionsExample Map, Acceptance Criteria, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
AgileIterationCadence
AlignmentArchitectureCanvas
Behavior-Driven DevelopmentRequirementsExamplesRefinement
CanvasArchitectureAlignmentWorkshop
Add more methods