PMP · Question #1161
One of the key stakeholders on the project team reaches out with an additional requirement that may impact the overall schedule. A discussion with another stakeholder suggests that this might just be
The correct answer is C. Request further clarification of the requirement.. When faced with a new requirement with conflicting initial assessments from stakeholders, the project manager must first seek precise clarification.
Question
One of the key stakeholders on the project team reaches out with an additional requirement that may impact the overall schedule. A discussion with another stakeholder suggests that this might just be a small task. What should the project manager do?
Options
- APerform a qualitative risk analysis.
- BCoordinate design document preparation.
- CRequest further clarification of the requirement.
- DManage the engagement of this stakeholder.
How the community answered
(49 responses)- A8% (4)
- B4% (2)
- C73% (36)
- D14% (7)
Why each option
When faced with a new requirement with conflicting initial assessments from stakeholders, the project manager must first seek precise clarification.
Performing qualitative risk analysis is premature; the requirement itself is not yet clearly defined or understood, so its risks cannot be accurately assessed.
Coordinating design document preparation is a step taken after a requirement is fully defined and approved, not when it's still unclear.
Before assessing impact or taking further action, the project manager must first gather complete and accurate information about the new requirement to understand its true nature and potential impact.
Managing stakeholder engagement is an ongoing process, but the immediate issue is the ambiguity of the requirement, not just engagement.
Concept tested: Requirement clarification and initial assessment
Topics
Community Discussion
5C is the right call here. In my experience managing enterprise rollouts, stakeholders constantly throw out requests and downplay the effort, but you never take someone's word that something is small without seeing the details yourself. Before you touch the schedule or loop in other teams, you need to understand exactly what is being asked and how it actually affects the work. A and D are things you might do eventually, but they come after you have a clear picture of the requirement itself.
D. Failed this exact trap first time, stakeholder engagement comes before clarification.
Actually C is the right call here, Wesley. In my experience managing projects, you need the requirements clarified before you can meaningfully engage stakeholders on a solution, otherwise you are just gathering opinions without a clear scope.
D all day. The stakeholder dynamic here is the real issue, one person says schedule impact, another says no big deal, so you manage the engagement to get alignment before anything else. No degree taught me that, but the PMP prep hammers it home.
Actually C is the right call here. When stakeholders are split on whether something is even a problem, you document it in the issue log first so there is a formal record, then you work the resolution and engagement from there. In practice if you skip logging it and just start managing relationships, you have no paper trail when it resurfaces.