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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
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.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-4 Wochen je Sprint, laufend1-3 h1-3 h45-90 min
Participantsdifferent
3-10 (Scrum Team)2-83-102-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalContext Map, Integration Patterns, Boundary NotesDomain Context Map, Boundary Notes, Ownership MapAnsoff Matrix, Growth Options, Risk Notes
Tagsno overlap
AgileIterationCadence
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignContextBoundaries
GrowthStrategyMarketPortfolio
Add more methods