View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Contextual Inquiry |  Agile Affinity Estimation |  Architecture C4 Model |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Low | Low |
Timedifferent | 1-3 Wochen | 30-90 min | 1-4 h | 2-5 min je Item |
Participantsdifferent | 4-12 Beobachtungen | 3-12 | 1-5 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Affinity Size Map, Grouped Estimates, Unclear Items | Context Diagram, Container Diagram, Component Diagram | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | UX researchObservationContext | EstimationBacklogRelative sizing | ArchitectureCommunicationVisualization | EstimationAgileRelative sizingTeam |