Study PMI-PBA Stakeholders and Decision Context: key concepts, common traps, and exam decision cues.
Chapter 2 moves from business need into stakeholder reality. PMI-PBA does not treat requirements as detached statements that appear on their own. The analyst has to know who should be represented, whose influence changes decisions, what different groups actually value, and where decision authority starts and stops. If that context is weak, later elicitation can look busy while still producing an incomplete or politically distorted requirement set.
The child lessons cover stakeholder identification, influence and representation, stakeholder values and tradeoffs, and alignment or decision boundaries. Together they show how stakeholder analysis becomes a control system for the whole effort: identify the full set of affected voices, understand which kind of influence each one has, surface the tradeoffs they are really protecting, and make the decision boundary explicit before governance misunderstandings harden.
PMI-PBA usually rewards analysts who treat stakeholder context as a source of decision quality, not as a soft interpersonal side topic. Strong answers usually widen representation, separate authority from expertise, expose value conflicts early, and use stakeholder evidence to improve later prioritization and planning.
Weak answers usually let the loudest or earliest voices define the initiative before the full context is understood, or confuse workshop attendance with real representation.