The correct answer is to facilitate a retrospective with the product owner and team to review the definition of done and acceptance criteria. This directly addresses the root cause of the agile product owner being dissatisfied with delivered features that yield no business value, as the team followed the prioritized backlog but clearly lacked a shared understanding of what “done” means. The retrospective creates a collaborative space to realign expectations, ensuring future increments meet the product owner’s value criteria through refined acceptance criteria. On the PMP exam, this scenario tests your grasp of agile principles like continuous improvement and stakeholder collaboration, often appearing as a trap where you might mistakenly re-prioritize the backlog or escalate. The key is recognizing that the backlog was followed correctly, so the misalignment lies in the definition of done, not the priorities. Memory tip: “Done before Done” — always verify the definition of done before assuming a feature delivers value.
PMP Process — Managing Technical Aspects Practice Question
This PMP practice question tests your understanding of process — managing technical aspects. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A project manager is leading a software development project using agile methodology. The team has completed 3 sprints, but the product owner is dissatisfied because the delivered features do not meet the expected business value. The team claims they followed the prioritized backlog. What should the project manager do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Facilitate a retrospective with the product owner and team to review the definition of done and acceptance criteria
The core issue is a misalignment between what the team delivered and what the product owner expects, despite following the prioritized backlog. The project manager should facilitate a retrospective to review the definition of done and acceptance criteria, as this ensures both parties have a shared understanding of what constitutes a completed, valuable feature. This aligns with agile principles of continuous improvement and stakeholder collaboration, directly addressing the root cause of the dissatisfaction.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Facilitate a retrospective with the product owner and team to review the definition of done and acceptance criteria
Why this is correct
A retrospective helps identify process improvements and realign on value delivery.
Related concept
Read the scenario before looking for a memorised answer.
✗
Create a detailed report showing the team's velocity and completed stories
Why it's wrong here
Reporting velocity does not address the gap between delivered features and business value.
✗
Replace the product owner with someone who has better domain knowledge
Why it's wrong here
This is a premature escalation; the issue may be process-related, not personnel.
✗
Ask the team to add more features to the next sprint to increase value
Why it's wrong here
Adding more features without addressing the root cause may not improve business value.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume the team is correct because they followed the backlog, and thus choose a metric-based or escalation option, missing the need for collaborative process improvement to realign expectations.
Detailed technical explanation
How to think about this question
In agile, the product owner is responsible for defining acceptance criteria and prioritizing the backlog, but the team must also validate that each user story meets the 'definition of done' (DoD) before it is considered complete. A common subtlety is that the DoD may be too technical (e.g., code merged, tests passed) without including business value validation (e.g., stakeholder demo, usability check). In a real-world scenario, a team might deliver a feature that passes all unit tests but fails to solve the user's core problem, leading to the product owner's dissatisfaction. The retrospective allows both parties to refine the DoD and acceptance criteria to include explicit business value checks.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the PMP exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this PMP question in full detail.
Process — Managing Technical Aspects — This question tests Process — Managing Technical Aspects — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Facilitate a retrospective with the product owner and team to review the definition of done and acceptance criteria — The core issue is a misalignment between what the team delivered and what the product owner expects, despite following the prioritized backlog. The project manager should facilitate a retrospective to review the definition of done and acceptance criteria, as this ensures both parties have a shared understanding of what constitutes a completed, valuable feature. This aligns with agile principles of continuous improvement and stakeholder collaboration, directly addressing the root cause of the dissatisfaction.
What should I do if I get this PMP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.