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 Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
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
Purposedifferent
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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-90 min15-60 min1-3 h1-3 h
Participantsdifferent
3-122-92-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsIdeal Day Estimates, Assumption Notes, Capacity CaveatsContext Map, Integration Patterns, Boundary NotesDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
EstimationBacklogRelative sizing
EstimationEffortAgile
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignContextBoundaries
Add more methods