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
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h30-90 min5-20 min1-3 h
Participantsdifferent
3-83-123-202-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesAffinity Size Map, Grouped Estimates, Unclear ItemsEffort Heatmap, Risk Signals, Discussion TargetsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignBoundariesModeling
EstimationBacklogRelative sizing
EstimationEffortRisk
Domain-Driven DesignBoundariesStrategy
Add more methods