PMP · Question #1349
A newly assigned project manager is reviewing the project management plan and realizes that the project is running behind schedule. What should the new project manager do to address this situation?
The correct answer is B. Modify the project management plan and get approval from relevant stakeholders.. Upon identifying a project running behind schedule, the new project manager must first analyze the situation, propose modifications to the project management plan, and secure stakeholder approval.
Question
Options
- ANegotiate with the project sponsor immediately and establish a new project charter.
- BModify the project management plan and get approval from relevant stakeholders.
- CIssue a change order to the change control board (CCB) and rebaseline the schedule.
- DAdd more resources to recover the schedule without making changes to the baseline.
How the community answered
(24 responses)- A13% (3)
- B79% (19)
- C4% (1)
- D4% (1)
Why each option
Upon identifying a project running behind schedule, the new project manager must first analyze the situation, propose modifications to the project management plan, and secure stakeholder approval.
Establishing a new project charter is extreme and typically reserved for major project re-initiation or cancellation, not for addressing schedule variance.
When a project is behind schedule, the project management plan needs to be revised to reflect the current reality and proposed recovery actions. This involves analyzing the variance, identifying corrective or preventive actions, updating relevant components of the plan (e.g., schedule, resource plan), and then obtaining formal approval from relevant stakeholders to ensure alignment and commitment to the new approach.
While issuing a change request (often to a CCB) to rebaseline the schedule is a part of addressing significant schedule deviations, it follows the analysis and proposed plan modifications, and it's specifically about rebaselining, which is a consequence of modifying the plan, not the first overarching action.
Adding more resources without analysis and plan modification is a reactive and potentially inefficient solution, and it implies making changes without formal approval or updating the official plan, which is poor project governance.
Concept tested: Project control and plan modification
Topics
Community Discussion
6B is correct. The new PM needs to treat the schedule variance as a program governance issue, which means modifying the project management plan through integrated change control and securing approval from relevant stakeholders so benefits realization stays aligned across component interdependencies.
B is the call here. Any adjustment to the plan flows through integrated change control, which means updating the plan with stakeholder approval rather than quietly rebaselining or adding bodies and hoping for the best.
B is correct because the PM needs to follow change control when the schedule is already behind and the plan needs updating. C sounds tempting with the CCB angle but issuing a change order is just one part of the process, and the PMI flow is to update the plan and get stakeholder approval first. A is wrong because you do not renegotiate the charter just because the schedule slipped, and D skips the formal change process entirely. One thing I am tracking in my review cards: does anyone know if the exam expects you to distinguish between modifying the plan under Perform Integrated Change Control versus rebaselining
B is correct. New PM must modify the plan and get stakeholder approval first.
I first leaned toward C because rebaselining sounds like the textbook fix for a schedule slip, but the stem just says the PM is reviewing the plan and realizing it is behind, which falls under Monitor and Control Project Work in Domain 3. B is correct because any update to the project management plan itself requires a change request and approval from relevant stakeholders, not an immediate CCB change order or unauthorized resource adds like D.
Agreed on B, and the key distinction worth a flashcard is that rebaselining in C is itself a change that requires the same change request approval, so C and D both fail for jumping straight to execution without the CR.