PMP · Question #489
A project manager finished reviewing the project deliverables for the current iteration with the customer. A new key stakeholder who just joined the customer's team, complains that the results do…
The correct answer is B. Conduct stakeholder identification and a project objectives review session. When a new key stakeholder expresses dissatisfaction with deliverables after an iteration review, the project manager should first identify the new stakeholder's expectations and review the project objectives to ensure alignment.
Question
A project manager finished reviewing the project deliverables for the current iteration with the customer. A new key stakeholder who just joined the customer's team, complains that the results do not provide the capabilities the business anticipated. What should the project manager do to address this issue?
Options
- ACreate a change request and update the scope management plan
- BConduct stakeholder identification and a project objectives review session
- CUpdate the stakeholder list and fix the deliverables
- DUpdate the project management plan and lessons learned
How the community answered
(31 responses)- A3% (1)
- B81% (25)
- C6% (2)
- D10% (3)
Why each option
When a new key stakeholder expresses dissatisfaction with deliverables after an iteration review, the project manager should first identify the new stakeholder's expectations and review the project objectives to ensure alignment.
Creating a change request and updating the scope management plan is a reactive step that assumes the new stakeholder's complaint is valid and represents a scope change, without first verifying if the complaint aligns with existing objectives or if the stakeholder's expectations are misaligned.
The arrival of a new key stakeholder who is dissatisfied requires the project manager to first understand their perspective and ensure alignment with the project's established goals. Conducting stakeholder identification helps formally onboard the new stakeholder and assess their influence and needs, while a project objectives review session clarifies the agreed-upon scope and deliverables, allowing for a structured discussion to address the perceived gap.
While updating the stakeholder list is necessary, immediately committing to "fix the deliverables" without understanding the new stakeholder's actual requirements or verifying them against the project's approved objectives could lead to unnecessary rework or scope creep.
Updating the project management plan and lessons learned are important documentation and continuous improvement activities, but they are not the immediate first step to engage with a new dissenting key stakeholder and address their concerns about deliverables.
Concept tested: Stakeholder engagement; managing new stakeholders
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/manage-stakeholder-engagement
Topics
Community Discussion
8
Prof. SaraJul 5, 2026B is correct because a new stakeholder complaining about missing capabilities means you have a gap in stakeholder engagement, not necessarily a scope defect. Use the mnemonic New Face, New Space to remember that a newly identified stakeholder requires formal identification and a review of project objectives to ensure alignment. Option C is a trap because fixing the deliverables assumes the work is actually wrong, when the real issue is that this stakeholder was never engaged during planning or iteration reviews. This maps to the People domain on the PMP blueprint under stakeholder engagement, so prioritize communication and alignment before touching the deliverables themselves.
Anjali D.Jul 5, 2026Our group landed on B. The new stakeholder was never properly identified or engaged, so you need to bring them into the fold and realign on project objectives before touching any deliverables.
Prof. SaraJul 8, 2026B is correct and fits Domain 4 (Stakeholder Management), but remember the mnemonic I.P. U.S. (Identify Plan Update Salience): before you realign objectives you must first formally Identify the stakeholder, run them through a Salience analysis, and Update the stakeholder register, otherwise you are engaging blind.
Wesley A.Jul 4, 2026Failed this one on my first attempt because I jumped straight to a change request like option A. The right move is B, you need to get the new stakeholder identified and make sure everyone is actually aligned on the project objectives before you go changing scope.
Yusuf A.Jul 5, 2026Going with D here. My lead showed me that when a new stakeholder surfaces a gap between expectations and deliverables, you update the project management plan to reflect what changed and capture lessons learned so the same misalignment does not happen in the next iteration. B sounds proactive but it stops short of actually documenting the adjustment, which is what the PM plan and lessons learned are for.
Anjali D.Jul 6, 2026B is correct here because when a stakeholder surfaces a gap between expectations and deliverables mid-iteration, your first move is to meet with them to understand and realign on expectations before you go updating any formal documents. D jumps straight to paperwork without actually addressing the misalignment with the stakeholder, which is why most of the group landed on B.
Brenda K.Jul 5, 2026C. Fresh stakeholder means update the list first, then fix deliverables. 30 seconds, flag and move.
Prof. SaraJul 6, 2026B is correct because a previously unknown stakeholder surfacing late means you engage them first to understand their concerns, then assess impact on deliverables, not just silently update a list. Remember the mnemonic U.I.A. for stakeholder changes: Understand, Impact, Act, which maps to the Communication and Stakeholder domains.