Unapproved Change Requests
Change proposals are documented as change requests; until a formal decision approves them, they remain unapproved and must not be implemented.
Key Points
- Requests for changes are logged as change requests and tracked through change control.
- No work should start on an unapproved change request.
- Impact analysis (scope, schedule, cost, risk, quality) is done before a decision is made.
- Each request is either approved, deferred, or rejected, and its status is communicated and recorded.
Example
A stakeholder asks to add an extra reporting field mid-sprint. The project manager documents it as a change request and queues it for the change control board. Until the board approves it, the team does not modify the backlog or deliverables.
PMP Example Question
Midway through execution, a stakeholder asks the team to immediately add a new feature. The project manager identifies this as an unapproved change request. What should the project manager do next?
- Implement the change to keep the stakeholder satisfied.
- Record the request, perform impact analysis, and submit it for formal approval before any work begins.
- Reject the request and close the ticket permanently.
- Ask the team to build a quick prototype while waiting for approval.
Correct Answer: B — Record, analyze impacts, and seek formal approval before implementation
Explanation: Unapproved change requests must not be implemented. They should be documented, analyzed, and sent through the formal change control process for a decision.
HKSM