PMP · Question #1209
A system migration project is in its closing stage. The project manager is being pressured to close the project. The project manager communicated to all stakeholders; however, the last department to…
The correct answer is B. Log the issue and assign it to the project team member(s). The project manager should formally log the communication issue and assign a team member to resolve it, ensuring all stakeholders are properly notified before the project officially closes.
Question
Options
- AClose out the project and tell the manager to open a service desk ticket.
- BLog the issue and assign it to the project team member(s).
- CEscalate the issue to the project sponsor and upper management.
- DReport the issue during the next status meeting at the end of the week.
How the community answered
(33 responses)- A3% (1)
- B79% (26)
- C12% (4)
- D6% (2)
Why each option
The project manager should formally log the communication issue and assign a team member to resolve it, ensuring all stakeholders are properly notified before the project officially closes.
Closing the project with an unresolved issue that impacts a key department is irresponsible and will lead to future problems and dissatisfaction.
The project cannot be properly closed if a critical stakeholder department has not received necessary communication regarding the migration completion. Logging this as an issue and assigning it to a team member ensures it is formally tracked and resolved, guaranteeing proper project closure and stakeholder satisfaction.
Escalating the issue to the project sponsor and upper management is premature for an operational communication problem that can likely be resolved by the project team.
Delaying the resolution until the next status meeting at the end of the week is inappropriate when the project is in its closing stage and under pressure, as immediate action is required.
Concept tested: Issue management during project closing
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
8B is correct because the PM communicated to all stakeholders, so this is a missed-delivery issue to track and assign, not a reason to halt closure or escalate. A and C both overreact to what the stem frames as a single department not receiving the notification, while D just delays the fix.
Leaned toward C first but B is right because its still an open issue needing tracking.
Agreed, B is the move. C is a trap because resolved or closed items dont need active tracking anymore.
I first leaned toward C because the pressure to close made it seem like an escalation situation, but the key word is "notification" which means not everyone was actually informed. B is correct because a department not receiving communication is an issue that needs to be logged and assigned to the team to resolve before you can properly close.
B is correct. Think of it like a postal carrier who discovers a piece of mail was never delivered to one house on the route, you don't just ignore it and tell the homeowner to figure it out, you log what went wrong and hand it back to the team to fix. In PMP terms, the PM must formally log the issue in the issue log and assign ownership for resolution rather than rushing to close out under pressure.
Good analogy but the real trap here is the answer that says "close the deliverable and document it in lessons learned" because that sounds responsible and people pick it under time pressure instead of catching that it skips the issue log entirely.
B is correct here because in closing you still need to log any open issues so they get properly handed off. The last department missed the notification, which is a real gap you cannot just brush aside by closing out and telling them to call the help desk. Logging it and assigning it to a team member keeps the issue tracked and actionable while still letting you move forward with the closeout process.
Spot on, B, and I would add the analogy of closing out a construction job but still filing a punch list item for the leaky faucet the plumbing subcontractor never got notified about, you log it so it does not vanish into thin air.