- Published on
Configuration vs Change Control — clean PMP separation
- Authors
- Name
- passpmpnow
One sentence you must memorize
- Configuration = keeping track of what things are
- Change Control = controlling decisions to modify those things
That’s it.
Why PMI separates them
Because in real companies configuration is an inventory.
Inventory = what do we have?
Change control = should we change any item in the inventory?
Example that always locks it in
| Topic | Configuration | Change Control |
|---|---|---|
| What | version, baseline, attributes, relationships | approval, authority, impact review |
| When | before / after changes | during the change decision |
| Who | CMDB / librarian / repository owner | CCB / governance body |
| Purpose | know what exists | control modification |
Exam trigger recognition
“Which process ensures we know which requirements version is current?”
→ Configuration mgmt.
“Which process ensures sponsor approval before modifying a requirement?”
→ Integrated Change Control.
Watch for this common trap
“Update documentation”
≠ change control decision.
Documentation update happens after the change authority approves.
Fast 3 steps PMI expects you to think
- Identify item → configuration
- Evaluate requested change → change control
- If approved → update configuration items again