PMP · Question #129
A project manager is assigned to a major construction project. The project is critical to the city's population, and especially to the local government official who committed to delivering the project
The correct answer is A. Meet with the new project sponsor to review the current project scope and the requested. Upon a new project sponsor's assignment and their desire to include new aspects, the project manager should first meet with the sponsor to review the current project scope against the requested changes.
Question
Options
- AMeet with the new project sponsor to review the current project scope and the requested
- BRebaseline the project as there is now a new project sponsor, which is presenting an opportunity
- CInvite the project sponsor to a briefing with the project team to demonstrate progress and seek
- DInform the new project sponsor that the new aspects will not be included in this project.
How the community answered
(38 responses)- A82% (31)
- B11% (4)
- C3% (1)
- D5% (2)
Why each option
Upon a new project sponsor's assignment and their desire to include new aspects, the project manager should first meet with the sponsor to review the current project scope against the requested changes.
The new project sponsor represents a critical stakeholder, and their requests can significantly impact the project. The project manager must engage directly with the sponsor to fully understand the proposed new aspects, review them in the context of the current project scope, objectives, and constraints, and determine their feasibility and impact before proceeding.
Rebaselining the project is a consequence of approved changes, not the first step in understanding new requests; discussion comes before action.
Inviting the sponsor to a team briefing before understanding their specific requests might be premature and less effective than a direct, focused discussion.
Immediately dismissing the new sponsor's requests is poor stakeholder management and could lead to conflict, especially given the sponsor's importance and influence.
Concept tested: Stakeholder engagement and scope management with new sponsor
Topics
Community Discussion
4A is the right call. New sponsor wants changes, you meet with them to review current scope and the requested additions before doing anything else. B trips people up because rebaselining sounds proactive but you dont rebaseline just because a new sponsor showed up, you do it after a formal change request goes through the process.
I first leaned toward C thinking you should get the sponsor up to speed with the team first, but the new aspects requested means you need to sit down with the sponsor and review scope before doing anything else. A is the only option that addresses the change request head on.
First leaned toward C because briefing the sponsor sounds collaborative, but the stem is really about a scope question, not a progress update. A wins because before you add or reject anything you meet with the sponsor to review the current scope against what they are asking for, which is straight change control process.
Agree on A and the change control logic, but worth noting people also grab B here because "assess impact" sounds procedural, when really the stem is testing whether you go to the sponsor first before doing anything else with the request.