Option D is the way to go. When there's a change in key stakeholders, especially with an executive and a milestone approval coming up, you need to brief them on the current project status first. A feels like a trap since risk assessment can wait until the new exec is informed. Pretty sure D aligns with best practices-let me know if you see it differently.
Q: 8
A project steering committee meeting was arranged to approve a milestone of a project within two
weeks. The project manager is informed that a new project executive will take over the project.
What should the project manager do first?
Options
Discussion
D. PMI always wants stakeholder engagement first, so briefing the new exec fits best here.
D , you brief the new exec ASAP to keep them engaged and aligned before any big milestone. Stakeholder engagement first. Agree?
Maybe D since the new exec is a key stakeholder for the milestone. A feels like a trap because risk assessment comes after realigning leadership, not before. Pretty sure PMI expects us to brief the new exec first, but happy to hear arguments.
D
D, Risk assessment is important but the exam expects immediate stakeholder engagement first, not A this time.
Its D, you brief the new exec first. Common trap is picking B, but change requests come after alignment with stakeholders.
D , briefing the new project exec comes before anything else when milestone approval is near.
Probably D. In PMI terms, stakeholder engagement takes priority, especially with a new executive who will influence milestone approval. You want the new decision maker to be informed and involved before any process changes. Makes sense to keep communication lines open first, but could see an argument for C in special cases.
C here. If the new exec brings changes, evaluating project impact might come first before anything else. Could be wrong though.
Be respectful. No spam.
Question 8 of 35