PMP · Question #222
A project scope statement has been approved, and the project manager and core team have been assigned to the project. Suddenly, the project manager takes a temporary leave of absence due to a medical
The correct answer is A. Ensure that the schedule is aligned with the vision and objectives.. After a temporary absence, the project manager returns to a nearly complete schedule developed by the team, whose priority is to ensure its alignment with the approved project vision and objectives.
Question
A project scope statement has been approved, and the project manager and core team have been assigned to the project. Suddenly, the project manager takes a temporary leave of absence due to a medical emergency. While the project manager is on leave, the team develops the project schedule. When the project manager returns, a detailed schedule is almost complete. What should the project manager do?
Options
- AEnsure that the schedule is aligned with the vision and objectives.
- BEscalate the compliance issue to the project management office (PMO).
- CCongratulate the team and move on to the execution phase.
- DDevelop a new detailed schedule with the team and project sponsor.
How the community answered
(35 responses)- A60% (21)
- B11% (4)
- C6% (2)
- D23% (8)
Why each option
After a temporary absence, the project manager returns to a nearly complete schedule developed by the team, whose priority is to ensure its alignment with the approved project vision and objectives.
Even if the team developed the schedule, the project manager remains ultimately accountable for the project's strategic alignment. Upon return, the project manager must meticulously review the nearly complete schedule to confirm it accurately reflects the approved scope, vision, and objectives, addressing any potential deviations before proceeding to execution.
Escalating a compliance issue is premature; the team acted proactively, and the PM's first step is review and validation, not assuming non-compliance.
Concept tested: Project schedule validation, scope alignment
Source: https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/define-features-epics?view=azure-devops
Topics
Community Discussion
7A is the right call here. When you get back from unexpected leave the first move is to verify the work matches the approved scope statement and project objectives, not rubber stamp it or blow it up. B is overkill since no real compliance violation happened, and D wastes effort tossing out a nearly complete schedule. Think of it like resuming a lab build after stepping away, you check that the config still matches your original design before you keep going.
Going with A. My senior always said the PM owns alignment, not just the schedule itself. Does anyone know if the exam still expects formal approval after a schedule is built without the PM?
Your senior is right about alignment, and the exam still expects the PM to drive schedule APPROVAL even if the actual building is delegated, so remember PA - PM Approves.
I picked C first because honestly the team got it done and you want to reward initiative, but the PMP exam always wants you to verify alignment with approved scope and objectives before accepting deliverables. A is the move because a schedule built without the PM in the room still has to tie back to what was approved.
A is correct here. The PM was out so the team built the schedule without the full picture, so first step is checking it against the approved scope statement and project objectives before accepting it. I had almost this exact scenario on my exam last month and B tempted me because I thought the team violated process, but the question is about what to do next, not assigning blame.
Going with C here, folks. The team built the schedule off an APPROVED scope statement, so the heavy lifting is done, and the PM walking in and scrapping it would tank morale. My memory hook: "Come back, Congratulate, Carry on" - the three C's of a PM returning to a team that held the fort!
Actually it is A, Fatima. An approved scope statement does not replace the WBS and project schedule the PM still needs to build with the team, so the right move is to sit down and work through the planning together rather than patting everyone on the back and moving on.