Eliciting Requirements

  • Use individual and group elicitation techniques
  • Discover and capture requirements with supporting details, including origin and rationale

Elicitation is the active process of drawing requirements out of stakeholders, not just waiting for them to be volunteered — individual techniques (interviews, observation, document analysis) suit deep, one-on-one input, while group techniques (workshops, focus groups, brainstorming) suit surfacing a wider range of input or resolving disagreement in real time. Matching the right technique to the situation is the core skill tested here.

A requirement captured without its origin and rationale — why it exists, who asked for it, what problem it solves — is much harder to evaluate, prioritize, or defend later when it's questioned or when trade-offs need to be made; good elicitation captures that supporting context at the same time as the requirement itself.

Study focus: a scenario describing a sensitive, individual concern being raised in a large group setting (or a broad, simple question being handled through expensive one-on-one interviews) is testing whether the right elicitation technique was chosen for the actual situation.

Key terms in this chapter

Elicitation technique · Individual elicitation · Group elicitation · Requirement rationale

Next: Analyzing and Decomposing Requirements

Try the free PMI-PBA practice questions · Take the free PMI-PBA mock exam