Study PMI-PBA Prioritization, Baselines, and Approval: key concepts, common traps, and exam decision cues.
Chapter 6 turns analysis into commitment. PMI-PBA expects analysts not only to understand requirements, but also to help the organization decide what is most important, what belongs now versus later, what becomes part of the official baseline, and what evidence stakeholders need before they approve that baseline. This is where business analysis starts to shape scope control directly.
The child lessons cover prioritization by value and risk, allocation across accepted, deferred, and rejected items, establishment of the requirements baseline, and approval or sign-off as a governed decision. Together they show how the analyst helps the organization turn a large requirement set into a controlled reference point rather than a vague collection of desired features.
This chapter links four disciplines that often fail when handled separately. Prioritization must reflect value, risk, and constraint together. Allocation must make acceptance and deferral visible. The baseline must be stable enough to support change control, testing, and coordination. Approval must be a real decision based on evidence and unresolved concerns, not a signature ritual. Strong analysts make those choices explicit. Weak answers let them happen informally in meeting language that nobody can later enforce.
That sequence matters. A weak analyst may talk about “approval” before the allocation logic is stable, or may call something a “baseline” before accepted and deferred items have really been separated. PMI-PBA tends to reward the analyst who can show how one decision creates the conditions for the next one. First the team prioritizes. Then it allocates realistically under constraint. Then it turns that allocation into a usable baseline. Then it seeks approval on something stakeholders can actually understand and govern.