This PMP-style scenario focuses on the project manager’s role in facilitating Agile collaboration and backlog management when the product owner introduces frequent new mandatory features during iterations.
📘 Scenario
During the third iteration of a project, the product owner requests another mandatory feature. This also happened in the previous two sprints, which resulted in failure and caused frustration within the team.
❓ Question
What should the project manager do next?
A. Request the scrum team to prioritize the product backlog
B. Ask the product owner to prioritize the backlog with the project team
C. Call for an internal meeting to discuss the changes and their value
D. Incorporate the changes in the last sprint before the first release
⚠️ Disclaimer: This PMP-style question is presented for educational and commentary purposes only. It is not sourced from any official PMI exam and is not intended to violate any copyright. This content reflects interpretations based on the PMI mindset and principles, and is designed to help learners prepare for the PMP exam. If this question resembles real PMP exam content, it is coincidental and used solely under the doctrine of fair use for academic discussion. No claim of affiliation with or endorsement by PMI is made.
✅ Correct Answer: B. Ask the product owner to prioritize the backlog with the project team
✅ Why B is the Best Answer
In Agile (Scrum), the Product Owner owns the product backlog and is responsible for prioritizing features based on business value.
However, changes should:
Be discussed collaboratively with the team
Occur during backlog refinement or sprint planning
Respect the team’s capacity and velocity
By having the product owner prioritize with the team, the project manager:
Ensures the team’s input is respected
Encourages collaboration and transparency
Prevents mid-sprint disruptions, which violate Scrum principles
This action reinforces agile values like collaboration, respect, and sustainable pace.
❌ Why Other Options Are Less Effective
A. Request the scrum team to prioritize the product backlog
🔻 Incorrect. The product owner owns backlog prioritization, not the Scrum team. The team can give input, but cannot take ownership of priority decisions.
C. Call for an internal meeting to discuss the changes and their value
🔻 Incomplete. While a meeting can help surface concerns, it doesn’t resolve the structural issue of backlog management and repeated mid-sprint changes. Direct collaboration with the product owner is needed.
D. Incorporate the changes in the last sprint before the first release
🔻 Risky. Accepting new features without reprioritizing can again jeopardize the sprint goal. This is reactive, not collaborative or strategic.
📌 Key Takeaways
Backlog prioritization is owned by the Product Owner
Sprint commitments must be respected — changes should go through backlog grooming, not injected mid-sprint
Team collaboration and transparency are core to Agile values
PMP candidates must understand Agile collaboration principles. Project managers must ensure that product owners and teams engage in prioritization to avoid sprint failures and protect delivery integrity.
PMP Referenced Question 22: Validating Budget Inputs for Analogous Estimation This PMP-style scenario focuses on avoiding estimation errors when using historical projects as a baseline. PMI...
PMP Referenced Question 21: Rebaselining a Delayed Project Through Change Control This PMP-style scenario focuses on how a project manager should respond when a project is...
PMP Referenced Question 19: Supporting Team Members Through Knowledge Gaps This PMP-style scenario tests how a project manager should respond to a team member’s performance issue...
PMP Referenced Question 18: Empowering Contractors Under Tight Project Deadlines This PMP-style scenario highlights best practices in empowering contracted teams during urgent rollouts. PMI encourages clear...
PMP Referenced Question 17: Ensuring Accurate and Accessible Project Documentation This PMP-style scenario challenges the project manager's responsibility in maintaining accurate, up-to-date, and accessible documentation, especially...