[Srinivas B Kulkarni] Possibility 1:- why po is interrupting during sprint we need to think on this at first

May be because po spent very little time during backlog refignment and was not in a position to prioritise the backlog and now he realise that priority is different and want the changes during sprint as a scrum master discuss and explain PO on his importance on deep discussion during refignmement

Possibility 2:- PO is in his new role and has minimal communication with end user later when end use raise queries he then come to developers during sprint

Possibility 3:- when SM skip to fasilitate backlog refignment it’s common PO can interrupt during sprint

Possibility 4:- backlog refignment and sprint planning done in absence of PO can be another possible way po interrupt during sprin

[Vijay Swaminathan] As a SM, I would try to understand the root cause why PO interrupts frequently.

1. There might be different possible reasons such as stakeholders pressure in adding scope/Tech Debt/Frequently occuring more PROD issues/ Not having courage to say "NO" to stakeholders walk-in requests etc.

2. Facilitate the discussion between Developers and PO to have shared understanding and ask questions " Is it really worth to address the interruptions even if it impacts the Sprint Goal"? If it is Yes and high priority, then facilitate the discussion to renegotiate the scope with PO and adapts Product Backlog by moving some PBI that is present in Sprint backlog currently and prioritize for next Sprint.

3. In Retrospective, facilitate the discussion with PO and team how to avoid these frequent interruptions in the upcoming sprints and have some working agreements with PO.

4. Coach PO to make him understanding the importance of Scrum Values and practices effectively.

[Shannon A.] I’d handle it with grace.

First, I’d observe and ask open ended questions and listen actively to figure out why the PO may be interrupting the sprint. Sometimes interruptions are misunderstandings or demonstrations of lack of communication. Is it something that, I, the Scrum Master can improve myself?

I’d probably say something like:
"I'd love to hear your thoughts on this and how we can create a balance between collaboration and allowing the Development Team to focus. What do you think would work best for you?”
Some questions may be:
“Can you share your perspective on our Sprint process?"
"How do you see your role in the Sprint process?"
“What challenges are you facing that are prompting sprint interruptions?"
I’d set clear sprint expectations and discuss the importance of minimal interruptions during the Sprint, emphasizing the need for focused work to meet Sprint goals.
Then, conclude by expressing appreciation for the PO’s contributions and willingness to work together on improving the process.

If it happened again, I’d encourage the PO to write down their questions or concerns as they arise during the Sprint on a visually engaging board or digital tool to discuss at a later time & work to improve the feedback loop.

[Garima Sahore] One of the possibility why the PO interrupts development team is unclear requirements. If that's the case then the PO needs to be coached on the importance of having an unchanged Acceptance criteria.

Other possibility can be (which I have experienced in one of my job) is PO is interested in quantifying development team work but not at all focused on what he is supposed to deliver. He is trying to add stuff in between the sprint which is unacceptable.

In both of these scenarios, The PO should be coached on what are his roles and responsibilities, Scrum principles and practices that should be followed.