How do I handle a stakeholder who constantly requests out of scope changes mid-sprint?

All answers to this question.

This is a classic communication breakdown. As a PM or Scrum Master, you must reinforce the role of the Product Owner. Every request must go through the backlog. I suggest having a private "educational" meeting with the executive. Explain how these "small favors" accumulate into significant delays that threaten the overall project deadline. Use data like your velocity charts to show the impact of past interruptions. It’s not about saying "no," but saying "not now, but we can add it to the next sprint planning."

   Answered 2025-02-05 by Amanda Roberts

Have you tried involving this stakeholder in the Sprint Review? Sometimes seeing the unfinished work caused by distractions makes the consequences more tangible for them.

   Answered 2025-02-08 by Christopher Lee

• That’s a sharp suggestion, Christopher. I’ll invite them to the next review. To answer your thought, I think seeing the "Definition of Done" not being met because of these side tasks will be a real eye-opener for them regarding team efficiency.

     Commented 2025-02-10 by Steven Hall

You need to empower your developers to say "Please talk to our PO." If the team doesn't hold the line, the executive will keep doing it. Consistency is key here.

   Answered 2025-02-12 by Barbara King

• Exactly, Barbara. A united front is essential. If even one developer says yes, it undermines the whole process. We implemented a "talk to the PO" policy and it worked wonders.

     Commented 2025-02-14 by Linda Garcia