PMP Stakeholder Engagement Practice Question
You are the project manager for a hybrid software development project. During sprint review, the product owner demonstrates a feature that meets the acceptance criteria but the key stakeholder expresses disappointment, saying it does not meet their expectations. What should the project manager do first?
⚠ Common exam trap
The trap is to assume that meeting acceptance criteria is sufficient; stakeholder satisfaction also requires managing expectations and continuous communication.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Schedule a meeting with the stakeholder to clarify their expectations and document any new requirements for future sprints.
To first understand the stakeholder's expectations and document them. This aligns with stakeholder engagement and scope management. Option A is incorrect because implementing changes without change control constitutes gold-plating and bypasses the change control process. Option C is incorrect because it dismisses the stakeholder's concerns, which could lead to dissatisfaction and reduce trust. Option D is incorrect because it bypasses the product owner's role and the proper change process; modifying the feature immediately without analysis is not appropriate. Therefore, scheduling a meeting to clarify expectations and document new requirements for future sprints is the best first step.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Approve the change yourself and add it to the current sprint backlog.
Why it's wrong here
Unilaterally approving a change and inserting it into the current sprint backlog is inappropriate for a Project Manager in a hybrid or agile environment. This action bypasses the Product Owner's authority in backlog management and sprint planning, potentially disrupting the sprint goal and team's focus. Such an approach lacks proper change control and can lead to uncontrolled scope creep, undermining the project's predictability and stability.
- ✓
Schedule a meeting with the stakeholder to clarify their expectations and document any new requirements for future sprints.
Why this is correct
This is the most appropriate action as it prioritizes effective stakeholder engagement and requirements management. By scheduling a meeting, the Project Manager can thoroughly understand the stakeholder's concerns and clarify their evolving expectations without immediately disrupting the current sprint. Documenting any new requirements ensures they are properly captured, evaluated, and prioritized for consideration in subsequent sprints, maintaining project agility and control.
- ✗
Explain that the feature meets the agreed acceptance criteria and close the discussion.
Why it's wrong here
While the feature may technically meet the established acceptance criteria, simply closing the discussion is poor stakeholder management and risks future dissatisfaction. This approach fails to acknowledge potential evolving needs, misinterpretations, or new insights from the stakeholder. Dismissing their concerns without further investigation can erode trust and miss opportunities to capture valuable feedback for future product enhancements.
- ✗
Ask the development team to modify the feature immediately to satisfy the stakeholder.
Why it's wrong here
Instructing the development team to immediately modify a feature based on an ad-hoc request is detrimental to sprint integrity and team productivity. This action introduces unplanned work, violates the principle of protecting the current sprint's scope and goal, and can lead to missed commitments or increased technical debt. Proper agile practice requires new requirements to be prioritized and planned for future iterations, not injected mid-sprint.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Change Control Process
A formal, structured procedure used to manage any changes to a project's scope, schedule, budget, or requirements, ensuring every modification is reviewed, approved, tested, and documented before implementation.
Key term
Scrum Methodology
Scrum is a lightweight process framework that helps teams deliver complex projects in small, iterative chunks called sprints.
About these practice questions
Courseiva writes every PMP question from scratch — 800 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMP exam.