PMP · Question #1162
A project manager is in the middle or handling a major upgrade to an existing product. The project manager learns that the resources initially promised as part or the project are being moved to anothe
The correct answer is A. Perform an impact analysis to see the effect on the project. When critical resources are unexpectedly reallocated, the project manager's immediate priority is to assess the potential consequences on the project.
Question
A project manager is in the middle or handling a major upgrade to an existing product. The project manager learns that the resources initially promised as part or the project are being moved to another priority project. What should the project manager do?
Options
- APerform an impact analysis to see the effect on the project
- BExamine ways of modifying the scope of the project.
- CAdopt a resource leveling procedure to level the resources
- DRetrieve the documentation that shows the resource allocation
How the community answered
(61 responses)- A84% (51)
- B10% (6)
- C5% (3)
- D2% (1)
Why each option
When critical resources are unexpectedly reallocated, the project manager's immediate priority is to assess the potential consequences on the project.
Losing promised resources is a significant change, and the project manager must first perform an impact analysis to understand how this will affect the project's schedule, budget, scope, and quality before deciding on corrective actions.
Modifying the scope might be a consequence of the impact, but it's not the first step; you need to understand what needs modifying and why after assessing the impact.
Resource leveling is typically used to optimize resource allocation within existing constraints, not to address a sudden loss of critical resources.
Retrieving documentation confirms the initial plan, but it doesn't solve the problem or determine the current project's future; the immediate need is to understand the impact of the change.
Concept tested: Change management and impact assessment
Topics
Community Discussion
4A is correct. Before touching scope or reshuffling resources you need to quantify the impact on schedule, cost, benefits realization, and downstream component interdependencies, and that analysis becomes your evidence base for governance escalation.
Saw this on my exam, picked A because PMI always wants impact analysis first.
Confirmed A on my exam last spring, and the wording was almost identical. The resource pullback is a classic trigger for impact analysis before you touch scope or start shuffling people around, since you need data to bring back to the sponsor.
Agreed on A, and the key is that impact analysis at the program level means mapping the ripple effects across all interdependent components, not just assessing the one project that lost the resource.