Protecting the Team from Ad-Hoc Stakeholder Requests: Work with Product Owner to Establish a Process
During a sprint retrospective, the team expresses frustration that they are frequently interrupted by ad-hoc requests from stakeholders. Scrum Master role you are also the PM. What should you do FIRST?
Quick Answer
The correct answer is to work with the product owner to establish a process for handling ad-hoc requests and shield the team. This is the first action because, as both Scrum Master and PM, your core responsibility is to protect the team from disruptions while still addressing stakeholder needs, which aligns with the servant-leader principle. By collaborating with the Product Owner to create a formal triage and prioritization process, you ensure non-critical requests are deferred to the product backlog rather than derailing the sprint. On the PMP exam, this scenario tests your understanding of stakeholder engagement and the Scrum Master’s role in maintaining team focus, often appearing as a trap where candidates mistakenly jump to coaching stakeholders directly or escalating to management. The key is to remember that the Product Owner owns the backlog, so you must work through them to filter requests. Memory tip: “PO for the flow, SM for the shield”—the Product Owner manages the request flow, while the Scrum Master shields the team.
⚠ Common exam trap
PMI often tests the misconception that a PM should directly control stakeholder requests or add buffers, rather than empowering the Product Owner to manage the backlog and the Scrum Master to shield the team.
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
✓
Work with the product owner to establish a process for handling ad-hoc requests and shield the team
As both Scrum Master and PM, your primary responsibility is to protect the team from disruptions while ensuring stakeholder needs are addressed. Working with the Product Owner to establish a formal process for handling ad-hoc requests—such as triaging, prioritizing, and deferring non-critical items—preserves the team's focus and sprint commitment. This aligns with the servant-leader role of a Scrum Master and the PM's duty to manage stakeholder expectations without bypassing the product backlog.
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 stakeholders to submit all requests as change requests for formal approval
Why it's wrong here
Routing every ad-hoc request through formal change control imposes heavyweight governance on routine stakeholder queries, which the Product Owner should first triage and shield the team from. Formal change requests are correct when a baselined scope, schedule or contract must be modified, not for everyday requests during a sprint.
- ✗
Instruct the team to ignore all ad-hoc requests until the next sprint planning
Why it's wrong here
Instructing the team to ignore requests removes the Product Owner's responsibility to evaluate and order them, and risks losing legitimate value or damaging stakeholder trust. Deliberate deferral is correct only when the Product Owner has already assessed the request and consciously placed it in the product backlog for future refinement.
- ✗
Add a buffer to the sprint backlog to account for interruptions
Why it's wrong here
Adding buffer capacity treats the symptom, not the cause, and inflates the sprint backlog without addressing why stakeholders bypass the Product Owner. A buffer would be the right response when interruptions are genuinely unavoidable and forecastable, such as planned operational support work with a known historical volume.
- ✓
Work with the product owner to establish a process for handling ad-hoc requests and shield the team
Why this is correct
Ad-hoc stakeholder requests bypass the backlog, so the product owner must triage them against sprint priorities. Establishing that intake process and shielding the team removes the interruption source, satisfying the stem's constraint of frequent mid-sprint disruptions.
Go deeper
Related to this question
Learn chapter
Team Building and Psychological Safety
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
One of 820 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 →
Same concept, more angles
2 more ways this is tested on PMP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. During a sprint retrospective, the team expresses frustration that they are frequently interrupted by unplanned support requests from the operations department. The product owner agrees this is impacting velocity. What should the project manager do FIRST?
medium- ✓ A.Work with the product owner to prioritize support requests and allocate a dedicated buffer for them.
- B.Escalate the issue to the project sponsor to negotiate with operations.
- C.Ask the team to track the time spent on support requests and report it at the next retrospective.
- D.Instruct the team to handle support requests as they come to maintain stakeholder satisfaction.
Why A: The immediate priority is to manage the unplanned work that is disrupting the sprint. By working with the product owner to prioritize support requests and allocate a dedicated buffer (e.g., a fixed capacity within the sprint backlog), the project manager ensures that the team can handle operational interruptions without derailing planned work. This aligns with the Agile principle of protecting the team's focus and using empirical data to adjust the process, rather than escalating or deferring action.
Variation 2. During a sprint retrospective, the team expresses frustration that they are frequently interrupted by unplanned work from other departments. The project manager wants to improve team focus. What should the project manager do?
easy- A.Increase the sprint duration to accommodate unplanned work
- B.Tell the team to ignore unplanned work requests
- C.Add a daily stand-up to discuss unplanned work
- ✓ D.Meet with other department managers to negotiate dedicated team time and establish a process for handling requests
Why D: It addresses the root cause of the team's frustration by negotiating dedicated team time with other departments and establishing a formal process for handling unplanned work requests. This aligns with the servant leadership approach in the People domain, where the project manager acts as a buffer and facilitator to protect the team's focus and productivity, rather than imposing a technical fix that ignores the systemic issue.
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.