Study PMI-PBA Document Control and Change Monitoring: key concepts, common traps, and exam decision cues.
On this page
Document control matters because weak versioning destroys trust in the analysis set. PMI-PBA usually rewards disciplined control of what changed, which version is approved, and how stakeholders can understand the current state of the requirements.
Monitoring is the live part of that discipline. Analysts should be able to explain what has shifted, what is stable, and which issues threaten alignment.
Stronger answers usually do
keep approved artifacts distinguishable from drafts
monitor requirement status and open issues over time
make version changes visible enough that stakeholders can reason about them
use monitoring to support decisions, not just archive history
Common traps
letting multiple “current” copies circulate
failing to show what actually changed between versions
treating status reporting as a one-time communication
allowing confusion over whether a requirement is approved, proposed, or obsolete