Stakeholder approaches mid-sprint with a feature request. What is the Scrum process?

WHAT THIS TESTS: This question tests whether you understand the separation of accountabilities in Scrum, specifically that the Product Owner owns the Product Backlog and ordering while the Developers own how they turn a selection of that work into an Increment of value during the Sprint. It also checks if you treat the Sprint as a container for a fixed selection of work rather than an open commitment to accept any new demand. Interviewers want to see that you protect the team from unplanned injection and that you know the formal channel for change.

A GOOD ANSWER COVERS: First, state clearly that as a Developer you do not accept the request yourself. Second, direct the stakeholder to the Product Owner because the Scrum Guide states that the Product Owner orders the work into a Product Backlog. Third, explain that the Scrum Team turns a selection of the work into an Increment of value during a Sprint, so the team does not unilaterally add new items to the current selection. Fourth, note that if the request is truly critical, the Product Owner may choose to add it to the Product Backlog and negotiate with the team, but that decision belongs to the Product Owner, not the stakeholder or the Developers.

COMMON WRONG ANSWERS: Saying you would size the request on the spot and squeeze it in shows you do not respect the Sprint boundary. Proposing a team vote to decide if it fits confuses collective ownership with Product Owner accountability. Claiming Scrum forbids any change ever is also wrong; adaptation is a pillar, but it is managed through the Product Owner and the Product Backlog, not through ad-hoc intake. Another red flag is saying you would ask the Scrum Master to shield you; the Scrum Master fosters the environment but does not own backlog decisions.

LIKELY FOLLOW-UPS: The interviewer may ask what happens if the Product Owner insists the new work must enter the current Sprint. In that case, the Product Owner and Developers renegotiate the scope of the current selection, potentially removing other work so the Sprint does not become overloaded. They may also ask how you handle the stakeholder relationship; the answer is to be helpful but firm, offering to attend a conversation with the Product Owner while making clear that the PO is the right person to prioritize value.

ONE CONCRETE EXAMPLE: Imagine a stakeholder asks you to add a one-click export button because a major client is threatening to churn. You respond by saying you understand the urgency and you will immediately connect them with the Product Owner. You do not provide an estimate or promise a timeline. The Product Owner adds the item to the Product Backlog, assesses its value against the current Sprint selection, and decides to swap out a lower priority story after discussing capacity with the Developers. The new work enters through the Product Backlog, not through a hallway conversation.