Study PMI-PBA Elicitation and Discovery: key concepts, common traps, and exam decision cues.
Chapter 4 is where analysis becomes evidence. PMI-PBA expects the analyst not only to choose methods well, but also to execute elicitation in a way that reveals real workflow detail, hidden assumptions, and the operational structure around the requirement set. That means knowing when one-to-one techniques are stronger than group sessions, how facilitated group work should expose disagreement instead of hiding it, how requirement statements should preserve source and rationale, and how constraints and dependencies should be surfaced before they distort the baseline.
The child lessons cover individual elicitation, group elicitation, capture of source and rationale, and discovery of constraints and dependencies. Together they show how elicitation becomes governed discovery rather than a series of meetings: pick the right interaction pattern, preserve why the requirement exists, and expose the operational conditions that will later affect prioritization, approval, and delivery.
One of the most exam-relevant PMI-PBA habits in this chapter is not confusing activity with discovery. Strong answers treat workshops, interviews, notes, and requirement statements as useful only when they reveal the real business logic, control points, and constraints that should shape the solution.
Weak answers usually celebrate stakeholder engagement volume without checking whether the information gathered is complete, credible, decision-ready, or strong enough to support later decomposition and prioritization.