View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Domain Context Map |  UX Research Contextual Inquiry |  Agile Affinity Estimation |  Agile Planning Poker |
|---|---|---|---|---|
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 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 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 Wochen | 30-90 min | 2-5 min je Item |
Participantsdifferent | 3-10 | 4-12 Beobachtungen | 3-12 | 3-9 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Field Notes, Workflow Insights, Pain Points | Affinity Size Map, Grouped Estimates, Unclear Items | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | Domain-Driven DesignContextBoundaries | UX researchObservationContext | EstimationBacklogRelative sizing | EstimationAgileRelative sizingTeam |