A predictive infrastructure project is midway through execution when a senior stakeholder emails the project manager directly and asks the team to add a small extra feature to a deliverable that is already baselined. The stakeholder says it is minor and can be slipped in quietly. What should the project manager do FIRST?
- AImplement the feature straight away because it is small and keeping a senior stakeholder satisfied protects the project's standing.
- BDecline the request outright and tell the stakeholder the baseline is fixed and cannot be reopened at this stage of the project.
- CAdd the feature to the product backlog so it can be prioritised and pulled into the next iteration by the team.
- DRaise a change request and route it through the integrated change control process so the impact on scope, schedule, and cost is assessed before any decision. Correct
Why A is wrong: Acting on a verbal request without assessment is unmanaged scope creep; even a small change can affect the schedule and cost baselines and must be evaluated before any work begins.
Why B is wrong: A flat refusal ignores that legitimate changes can be approved through the proper process; the correct step is to assess the request, not to reject it before analysis.
Why C is wrong: A backlog and iterations belong to an adaptive approach; this is a predictive project with a baseline, so the change belongs in integrated change control, not a backlog.
Why D is correct: In a predictive project every baseline change flows through integrated change control, where the impact is analysed and the change control board decides, keeping the baselines authoritative.