PMP People — Leading Projects Practice Question
During a sprint retrospective, the team identifies that unclear requirements from the product owner are causing rework. The team suggests improvements. Which THREE actions should the project manager (Scrum Master) take?
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
✓
Introduce a requirements clarification step before each sprint planning
Options C, D, and E are correct because they address the root cause of unclear requirements: adding a clarification step before sprint planning, implementing one of the team's suggested improvements per sprint, and ensuring the product owner attends all planning and grooming sessions to clarify requirements in real time. Option A is incorrect because adding buffer time does not prevent rework; it only accommodates it. Option B is incorrect because proceeding with best interpretation invites further rework and violates the principle of transparency.
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 buffer time to the sprint plan to accommodate potential rework
Why it's wrong here
This approach is a reactive measure that accommodates the symptom (rework due to unclear requirements) rather than addressing its root cause. While buffers might temporarily absorb some impact, they do not improve the clarity of requirements or prevent future rework, which is contrary to agile principles of continuous improvement and waste reduction. A PMP focuses on preventing issues, not just mitigating their symptoms.
- ✗
Instruct the team to proceed with their best interpretation of requirements
Why it's wrong here
Instructing the team to proceed with their best interpretation without seeking clarification is highly detrimental, as it significantly increases the likelihood of building the wrong features or requiring extensive rework. This approach shifts the burden of ambiguity onto the development team, leading to potential frustration and decreased product quality. The Project Manager's role is to facilitate clear communication and ensure requirements are understood, not to encourage assumptions.
- ✓
Introduce a requirements clarification step before each sprint planning
Why this is correct
Introducing a dedicated requirements clarification step before sprint planning is a proactive and preventative measure that aligns with agile principles. This ensures that the Product Backlog items selected for the upcoming sprint are thoroughly understood by the development team, reducing ambiguity and the likelihood of rework during the sprint. It "shifts left" the identification and resolution of requirement issues, improving efficiency and quality.
- ✓
Work with the product owner to implement one of the team's suggested improvements in the next sprint
Why this is correct
This option directly embodies the core agile principle of continuous improvement, which is the primary purpose of a sprint retrospective. By collaborating with the Product Owner to implement a team-suggested improvement, the project manager ensures that lessons learned are translated into actionable changes. This iterative approach fosters a culture of adaptation and problem-solving, directly addressing the root cause of unclear requirements over time.
- ✓
Ensure the product owner attends all sprint planning and grooming sessions to clarify requirements
Why this is correct
The Product Owner is the authoritative source for product requirements and the voice of the customer; therefore, their consistent presence in sprint planning and backlog refinement (grooming) sessions is critical. This direct involvement enables immediate clarification of ambiguities, ensures a shared understanding of user stories, and helps the development team make informed decisions. Their active participation significantly reduces the risk of misinterpretation and subsequent rework.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Sprint Retrospective
A Sprint Retrospective is a time-boxed meeting at the end of a Scrum sprint where the team reflects on their process and identifies improvements for the next sprint.
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
This PMP question is part of Courseiva's 800-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.