Elicitation and Collaboration
Describes the tasks BAs perform to obtain information from stakeholders, confirm the results, and communicate BA information so that everyone shares an accurate, up-to-date understanding.
Draws information out of stakeholders and keeps everyone aligned on what it means.
Requirements rarely arrive pre-formed; they have to be elicited, confirmed, and then communicated back without distortion. This KA is where the BA's craft is most visible, and where most projects quietly fail when the BA stops at note-taking instead of confirming and communicating.
In practice
Elicitation is planned (right technique, right participants, right artefacts), conducted (interview, workshop, observation, document analysis), confirmed (back to the source) and then communicated (to the people who will design, build, test or approve). Collaboration is ongoing — not a phase.
Relationships with other knowledge areas
- →Receives the engagement plan and stakeholder analysis from BAPM.
- →Feeds raw and confirmed information into Requirements Life Cycle Management.
- →Provides the qualitative evidence that Strategy Analysis turns into a change strategy.
- →Loops back from Solution Evaluation when measured results contradict assumptions.
Where this lands on the exam
BACCM touchpoints
- Stakeholder. Stakeholders are the source and the audience of every elicitation activity.
- Need. Elicitation surfaces underlying needs hidden behind stated solutions.
- Value. Communication keeps value visible to the people who fund and accept the change.
Language to listen for in scenario stems
When a stem describes a meeting, workshop, interview, or 'getting information from / to' stakeholders, it is testing Elicitation & Collaboration.
Key concepts
The ideas that anchor everything else in this knowledge area.
Information is rarely complete after the first pass. Plan for multiple rounds, expect new information, and confirm before acting.
Collaborative (workshops, focus groups), research (document analysis, market research), and experimentation (prototyping, observation).
Communication confirms shared understanding. Sending a document is not communication if no one engages with it.
Stakeholder relationships are managed continuously, not only at kickoff.
Common pitfalls
Patterns that frequently cost initiatives — and exam points.
- ⚠Stopping at the first answer instead of probing for the underlying need.
- ⚠Confusing 'we shared the doc' with 'we confirmed understanding'.
- ⚠Choosing the elicitation technique you're comfortable with, not the one that fits.
- ⚠Over-relying on one stakeholder — missing dissenting views.
Tasks
The 5 tasks that make up this knowledge area. Click any task to expand its inputs, outputs, techniques, and guidelines. Technique tags are clickable.