5.3. Manage and Control Changes
💡 First Principle: Change control exists to prevent silent scope drift — every enabler in this task is about making change visible, deliberate, and documented, because an undocumented "small" change is how uncontrolled scope creep actually happens.
Enablers: execute the change-control process, communicate the status of proposed changes, implement approved changes, and update project documentation to reflect changes.
"Communicate the status of proposed changes" is easy to under-value: stakeholders who submitted a change request and hear nothing back lose trust in the process and start routing around it informally — which is exactly the uncontrolled-change pathway this task exists to prevent.
⚠️ Exam Trap: Implementing a change once it's "clearly a good idea" without running it through the formal change-control process, even under time pressure. Bypassing the process — even for a beneficial change — is the trap PMI tests for.
