PMP Process — Managing Technical Aspects Practice Question
In your Scrum project, the development team has been consistently missing sprint commitments. During the retrospective, the team identifies that scope is often added during the sprint by the product owner without consulting the team. What should you do as the Scrum Master?
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
✓
Coach the product owner on the importance of not changing scope during a sprint.
The Scrum Master is responsible for protecting the team and ensuring the Scrum process is followed. The product owner should not add scope during a sprint; changes should be deferred to the next sprint. The Scrum Master should coach the product owner.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ask the product owner to stop attending daily standups to prevent scope changes.
Why it's wrong here
Excluding the Product Owner from the Daily Scrum is counterproductive to Scrum's principles of transparency and collaboration. While the Daily Scrum is primarily for the Development Team to plan their day, the Product Owner's presence as an observer can foster understanding and alignment. Preventing their attendance does not address the root cause of scope changes and instead creates an information silo, hindering effective communication and shared understanding of progress and impediments.
- ✗
Update the sprint backlog to reflect the changes and extend the sprint duration.
Why it's wrong here
Modifying the Sprint Backlog to incorporate new scope and extending the sprint duration fundamentally undermines the Sprint Goal and the time-boxed nature of a sprint. The Sprint Backlog represents the Development Team's forecast of work to achieve a specific Sprint Goal within a fixed timeframe. Such changes disrupt the team's focus, compromise predictability, and prevent the team from learning to accurately forecast and commit to work, thereby weakening the entire Scrum framework.
- ✗
Allow the product owner to add scope if the team agrees.
Why it's wrong here
Even with the Development Team's agreement, adding new scope during a sprint is generally discouraged as it jeopardizes the Sprint Goal and the team's ability to deliver a "Done" Increment. The Sprint Goal is a commitment established at Sprint Planning, providing focus and stability. While minor clarifications or re-prioritization of existing scope might occur, introducing entirely new work, regardless of team consensus, can lead to overcommitment, reduced quality, and failure to meet the original Sprint Goal.
- ✓
Coach the product owner on the importance of not changing scope during a sprint.
Why this is correct
This is the most appropriate action for a Scrum Master. The Scrum Master's role includes coaching the Product Owner on Scrum principles and practices, emphasizing the importance of the Sprint Goal and the detrimental impact of mid-sprint scope changes. Educating the Product Owner about how such changes disrupt the Development Team's focus, reduce predictability, and compromise the integrity of the sprint commitment fosters a better understanding of Scrum and promotes healthier team dynamics.
Go deeper
Related to this question
About these practice questions
One of 800 original PMP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.