Elicitation and Collaboration: Getting Information and Keeping People With You
This domain tests how the analyst obtains information and sustains stakeholder cooperation through the change. BABOK Guide v3 defines five tasks: Prepare for Elicitation, Conduct Elicitation, Confirm Elicitation Results, Communicate Business Analysis Information, and Manage Stakeholder Collaboration. Questions typically probe technique selection, what confirmation actually requires, and how to tailor communication.
The task flow
- Prepare - clarify the purpose and scope of the activity, choose techniques, confirm participants and logistics, assemble materials. Output: elicitation activity plan.
- Conduct - BABOK v3 groups elicitation into collaborative, research, and experimental forms. Interviews and workshops are collaborative; document analysis and questionnaires are research; prototyping and observation are experimental. Interactive techniques suit small, available groups; questionnaires suit large, dispersed populations; observation surfaces tacit, habitual work.
- Confirm - compare results against the source, resolve contradictions, close gaps, and record the confirmed results. This is a real analysis step, not a formality.
- Communicate Business Analysis Information - adjust format, level of detail, and formality to each audience, and check that the message landed.
- Manage Stakeholder Collaboration - monitor engagement, surface and resolve conflict, negotiate commitments, and keep working relationships productive.
Worked example
A logistics firm is building a driver app. Warehouse managers insist paper manifests are obsolete, and drivers never mention printing. Observation at depots shows drivers printing every morning because mobile signal is poor. The BA records offline capability as a non-functional requirement and confirms it with the drivers in a follow-up interview. The reasoning: interviews captured stated needs, observation captured actual behaviour, and confirmation closed the gap between the two.
Traps that cost marks
- Treating confirmation as a signature. It requires checking consistency, resolving conflicts, and identifying missing information.
- Selecting a workshop for fifty dispersed stakeholders, or a questionnaire when you need to probe reasons in depth.
- Assuming the sponsor's account represents all stakeholders.
- Forgetting that elicitation also verifies and elaborates requirements you already hold, and that preparation is a scored task in its own right.
- Assuming silence means agreement.