PMP People — Leading Projects Practice Question
An agile project team is in the middle of a sprint when the product owner introduces a high-priority change that was not part of the sprint backlog. The team is concerned about their ability to deliver the sprint goal. Which TWO options align with the Scrum framework? (Choose two.)
⚠ Common exam trap
Watch out — candidates often confuse the Product Owner's authority to re-prioritize the Product Backlog with the ability to change the Sprint Backlog mid-sprint, leading them to select options like B or D that violate the Sprint's immutability and the team's commitment to the Sprint Goal.
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
✓
The product owner cancels the current sprint and starts a new sprint with the revised backlog
The Scrum framework explicitly allows the Product Owner to cancel a sprint if the Sprint Goal becomes obsolete, such as when a high-priority change emerges that invalidates the current goal. Cancelling the sprint and starting a new one with the revised backlog ensures the team focuses on the highest-value work without disrupting the sprint's time-box or overloading the team. Option E is correct because the Product Owner can add the new work to the Product Backlog and prioritize it for the next sprint, which respects the current Sprint's commitment and allows the team to complete the Sprint Goal without interruption.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The product owner cancels the current sprint and starts a new sprint with the revised backlog
Why this is correct
When the sprint goal becomes obsolete due to significant new information, the Product Owner has the authority to cancel the sprint. This action ensures the team is always working on the most valuable items, preventing wasted effort on an invalidated goal. A new sprint can then be initiated with a refined backlog reflecting the updated priorities.
- ✗
Replace the least important sprint backlog item with the new work and adjust the sprint goal accordingly
Why it's wrong here
Replacing sprint backlog items mid-sprint fundamentally undermines the Development Team's commitment to the sprint goal and the integrity of the sprint itself. The sprint backlog is a forecast of work to achieve the sprint goal, and arbitrarily swapping items disrupts the team's planned work, potentially leading to incomplete features, rework, and a loss of focus.
- ✗
Instruct the team to include the new work in the current sprint and extend the sprint duration
Why it's wrong here
Extending the sprint duration directly violates the Scrum principle of time-boxing, which mandates fixed-length sprints to create rhythm and predictability. Altering the sprint length mid-sprint disrupts the team's cadence, makes forecasting difficult, and can mask underlying issues with sprint planning or scope management rather than addressing them effectively.
- ✗
Add the new work to the sprint backlog and ask the team to work overtime
Why it's wrong here
Adding new work to the sprint backlog mid-sprint without adjusting the sprint goal or scope compromises the Development Team's ability to achieve their committed forecast. Furthermore, routinely asking the team to work overtime to accommodate unplanned scope additions is an unsustainable practice that leads to burnout, reduced quality, and a breakdown of trust within the team.
- ✓
The product owner adds the new work to the product backlog and prioritizes it for the next sprint
Why this is correct
The most common and preferred approach in Scrum for handling new work during a sprint is for the Product Owner to add it to the product backlog. This allows the current sprint to maintain its integrity and focus on its committed sprint goal. The new item can then be refined, estimated, and properly prioritized for consideration in a future sprint, ensuring a stable workflow.
Go deeper
Related to this question
Learn chapter
Introduction to the PMP Exam and Project Management Basics
Key term
Sprint Planning
Sprint Planning is a time-boxed meeting at the start of a Scrum sprint where the team decides what work they can deliver and how they will do it.
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.