HKSM
Update
A change made to a deliverable, a component of the project management plan, or a project document that is not subject to formal change control.
Key Points
- No formal change request or board approval is required because the item is not baselined or formally controlled.
- Should be recorded through versioning or a revision history to maintain transparency and traceability.
- Commonly applied to project documents such as the issue log, risk register entries, stakeholder register, or team directory.
- Must not change baselines or other controlled artifacts; those require formal change control.
Example
After a stakeholder meeting, the project manager adds a new stakeholder and updates contact details in the stakeholder register. The revision is dated and noted, but no change request is submitted because the register is not under formal change control.
PMP Example Question
During execution, a tester adds a newly discovered defect to the issue log and updates its priority without submitting a change request. What is this action called?
- Update
- Change request
- Corrective action
- Preventive action
Correct Answer: A — Update
Explanation: The issue log is typically not under formal change control, so revising it is an update, not a formal change request or corrective/preventive action.
