What is the best way to handle a Product Owner who constantly changes priorities mid-sprint?

All answers to this question.

This is a classic coaching opportunity. You need to show the PO the "Data of Disruption." Track how much velocity is lost every time a priority shifts mid-sprint. During a 1-on-1, explain that the Sprint Goal is a commitment to a specific outcome. If the goal changes, the commitment is void. Suggest a "Buffer" for urgent items if the industry is truly volatile, or move to shorter one-week sprints. This gives the PO the flexibility they need while protecting the team's focus. Remind them that constant context switching is the fastest way to increase bugs and technical debt in the long run.

   Answered 2025-08-12 by Amanda White

Data is powerful, but what if the PO is under extreme pressure from the C-suite? Have you considered inviting the stakeholders to the Sprint Review so they can see the impact of their "urgent" requests on the actual product increment being delivered?

   Answered 2025-08-14 by Thomas Wright

• Thomas, we actually tried that! We started a "Stakeholder Impact" section in our reviews. When the executives saw that their last-minute change delayed a major feature by two sprints, they became much more disciplined. It turned the conversation from 'no' to 'later,' which worked wonders for our team morale.

     Commented 2025-08-16 by Cynthia Rogers

The Scrum Guide is clear that the Sprint Goal should not be endangered. If the change is that big, the sprint should be cancelled and re-planned, though that is a nuclear option.

   Answered 2025-08-18 by Robert Wilson

• True, Robert. Sometimes just mentioning the possibility of a "Sprint Cancellation" is enough to make a PO reconsider if that 'emergency' feature is truly worth the cost of stopping all progress.

     Commented 2024-08-20 by Amanda White