How do I handle a Product Owner who constantly changes priorities during an active Sprint?

All answers to this question.

I’ve faced this exact scenario at my previous firm. The key is to steer the conversation back to the Sprint Goal. When the PO tries to add a new story, I visually demonstrate the impact on the Burndown Chart. It's not about saying "no," but rather "what are we removing to make room for this?" If they insist on the change, you might need to suggest a Sprint Cancellation if the goal is no longer valid, which usually makes the PO reconsider the urgency of the new request.

   Answered 2024-03-15 by Rebecca Miller

That sounds incredibly frustrating for the developers. Have you tried setting up a formal Backlog Refinement session to ensure the PO has a space to vet these ideas before they hit the Sprint?

   Answered 2024-03-16 by Mark Thompson

• Mark, we do have refinement once a week, but the PO often gets "emergency" requests from the C-suite that they feel they can't ignore. It’s the external pressure that’s the real culprit here. I’m trying to coach the PO on shielding the team, but it’s a slow process.

     Commented 2024-03-17 by Sarah Jenkins

The Scrum Guide is clear: only the Developers can change the Sprint Backlog. Remind the PO of the "Definition of Ready" to stop half-baked ideas from sneaking in.

   Answered 2024-03-18 by David Clarkson

• Exactly, David! Enforcing the "Definition of Ready" is a game-changer. It forces the PO to provide clear acceptance criteria before the team even looks at the task.

     Commented 2024-03-19 by Rebecca Miller