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 Bucket System.
Agile
Bucket System
Paper illustration for Contextual Inquiry.
UX Research
Contextual Inquiry
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 a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
30-90 min30-90 min1-3 Wochen1-3 h
Participantsdifferent
3-123-124-12 Beobachtungen3-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsBucketed Backlog, Relative Estimates, Split CandidatesField Notes, Workflow Insights, Pain PointsDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
EstimationBacklogRelative sizing
EstimationBacklogRelative sizing
UX researchObservationContext
Domain-Driven DesignContextBoundaries
Add more methods