PMP · Question #463
During the implementation phase of a project, a new regulation affects the project, and a critical status meeting discussing the scope changes is required. The project manager discovers that a key…
The correct answer is D. Meet with the stakeholder prior to the meeting to obtain their opinion. When a key stakeholder cannot attend a critical meeting on scope changes, the project manager should proactively meet with them beforehand to gather their input and ensure their perspective is represented. This ensures the stakeholder's critical input is not missed and…
Question
Options
- ACall for a change control board (CCB) meeting, and inform the stakeholder about the outcome
- BUpdate the communications management plan and implement the change
- CMeet with the project sponsor to discuss how to address the situation
- DMeet with the stakeholder prior to the meeting to obtain their opinion
How the community answered
(32 responses)- A6% (2)
- B3% (1)
- C9% (3)
- D81% (26)
Why each option
When a key stakeholder cannot attend a critical meeting on scope changes, the project manager should proactively meet with them beforehand to gather their input and ensure their perspective is represented. This ensures the stakeholder's critical input is not missed and maintains their engagement despite their absence from the main meeting.
A CCB meeting would typically occur after the scope changes have been discussed and proposed, and merely informing the stakeholder about the outcome without their input is poor stakeholder engagement.
Updating the communications management plan is a process improvement activity, not an immediate solution to gather a key stakeholder's critical input on scope changes.
While the project sponsor is important, they might not have the specific insights or authority of the key stakeholder regarding the specific scope changes. The immediate need is to capture the key stakeholder's input.
A key stakeholder's input on critical scope changes is vital for project success and buy-in. Meeting with the stakeholder prior to the main meeting allows the project manager to gather their opinions, understand their concerns, and represent their views during the discussion, ensuring their influence is still incorporated.
Concept tested: Stakeholder engagement, critical input management
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
6D is correct. A key stakeholder missing a critical scope change meeting does not mean their input gets skipped, so you meet with them beforehand to capture their position and bring it to the table. I always tell folks in my study group, if you want to see why this matters, spin up a quick mock project in a sandbox and simulate a stakeholder no-show on a regulatory change, it clicks fast when you run it yourself.
Good call on D, and the pre-meeting capture maps directly to Domain 3 stakeholder engagement, though I would add one nuance, document their position in writing beforehand so there is a traceable record to bring to the table, not just your verbal summary.
D is correct. A key stakeholder missing a critical scope meeting means you must get their input beforehand. PMI prefers proactive stakeholder engagement over proceeding without them or escalating to the sponsor.
Agreed on D, but want to make sure I understand: the proactive piece is documenting their input beforehand so the meeting can still proceed on schedule, not delaying the meeting itself, right?
Going with B. The comms plan should reflect stakeholder availability before implementing changes.
D is correct here because the comms plan needs to reflect stakeholder communication requirements, not just availability. Nina, availability matters but it is a subset of what you assess, the real driver is mapping what each stakeholder actually needs to receive.