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 Domain Context Map
Domain Modeling
Domain Context Map
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
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.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.On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h1-3 h15-45 min5-20 min
Participantsdifferent
3-102-81-83-20
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Domain Context Map, Boundary Notes, Ownership MapContext Map, Integration Patterns, Boundary NotesPERT Estimate, Expected Value, Risk NotesEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesStrategy
EstimationUncertaintyRisk
EstimationEffortRisk
Add more methods