PMP Process — Managing Technical Aspects Practice Question
You are managing a software development project using Scrum. During the sprint review, the product owner praises the team's work but mentions that a key stakeholder is unhappy because an expected feature was delivered with limited functionality. The feature was completed according to the sprint backlog, but the stakeholder had not communicated their detailed expectations. What should you do FIRST?
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 expectations and discuss how to incorporate their feedback into the product backlog
The correct first step because the issue stems from a communication gap. Scheduling a meeting with the stakeholder allows the project manager to understand the detailed expectations that were not communicated, and to discuss how to incorporate the feedback into the product backlog for future sprints. This aligns with the Agile principle of continuous stakeholder involvement and iterative refinement. Option A is incorrect because adding features without formal approval bypasses the product owner's role and the backlog prioritization process. Option B is too passive; simply updating the issue log does not address the underlying expectation gap. Option C escalates prematurely before attempting direct communication with the stakeholder.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add the missing features to the next sprint without formal approval to satisfy the stakeholder immediately
Why it's wrong here
Adding features to the next sprint without formal approval bypasses critical agile governance and backlog management processes. This action undermines the Product Owner's authority to prioritize the product backlog based on value, feasibility, and strategic alignment. Furthermore, it can disrupt the development team's sprint commitment, lead to scope creep, and negatively impact team morale and predictability, violating principles of transparency and sustainable pace.
- ✗
Update the issue log and move on, since the team delivered the scope as planned
Why it's wrong here
Simply updating the issue log and moving on, despite stakeholder dissatisfaction, demonstrates a reactive and inadequate approach to project management. Even if the initial scope was technically delivered, ignoring a stakeholder's unmet expectations or perceived missing features can erode trust, diminish the perceived value of the deliverable, and lead to future resistance or rejection. Effective project management requires proactive engagement to ensure stakeholder satisfaction and successful product adoption.
- ✗
Escalate the issue to the project sponsor as a risk that the stakeholder may reject the deliverable
Why it's wrong here
Escalating the issue directly to the project sponsor at this stage is premature and bypasses the opportunity for direct, collaborative problem-solving with the affected stakeholder. Such an action can strain relationships, create unnecessary alarm, and consume higher-level resources before attempts have been made to understand the root cause and resolve the concern at the operational level. Effective issue management prioritizes direct communication and resolution before escalation.
- ✓
Schedule a meeting with the stakeholder to clarify expectations and discuss how to incorporate their feedback into the product backlog
Why this is correct
Scheduling a meeting with the stakeholder is the most appropriate first step, aligning with agile principles of continuous communication and collaboration. This proactive engagement allows for clarification of expectations, identification of the specific feedback or missing features, and a structured discussion on how to incorporate these into the product backlog. This approach ensures transparency, manages expectations, and leverages the agile framework for iterative improvement and value delivery.
Go deeper
Related to this question
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.