How do you handle a mid-Sprint urgent feature request?

WHAT THIS TESTS: This question tests whether you protect the Scrum framework from ad-hoc changes or silently discard rules when pressure appears. The interviewer wants to see that you respect the Product Owner's accountability for ordering work into the Product Backlog and that you treat the Sprint as a container for a fixed selection of work rather than an open pipeline. It also checks your grasp of empiricism: making the request visible so the team can inspect and adapt.

A GOOD ANSWER COVERS: A strong answer hits four things in order. First, listen to the stakeholder with respect and gather context without promising delivery. Second, redirect the stakeholder to the Product Owner because the Scrum Guide states that the Product Owner orders the work for a complex problem into a Product Backlog. Third, refuse to add the item directly to the Sprint Backlog yourself; the current selection is what the Scrum Team turned into an Increment during the Sprint, and changing that selection mid-flight covers up problems rather than solving them. Fourth, offer transparency by making the request visible to the Scrum Team so it can be inspected and adapted for the next Sprint.

COMMON WRONG ANSWERS: The biggest red flag is agreeing to squeeze the feature in immediately to keep the stakeholder happy. Another failure is saying you would add it to the Sprint Backlog and just work extra hours, because that changes the core design of Scrum and limits its benefits. A third red flag is claiming you would unilaterally drop an existing Sprint item to make room; the Product Owner orders work, so a developer should not make that trade-off alone.

LIKELY FOLLOW-UPS: The interviewer may ask what you would do if the stakeholder is your CEO or if the Product Owner is absent. They may also ask how you would handle a genuine emergency that truly endangers the Sprint Goal, or how you would explain the cost of context switching to a non-technical stakeholder. Be ready to discuss how Scrum makes visible the relative efficacy of current management techniques so that stakeholders learn to plan ahead.

ONE CONCRETE EXAMPLE: Imagine a VP of Sales asks you to add an urgent export button on day three of a two-week Sprint. You reply that you understand the urgency, explain that the Product Owner owns ordering decisions, and offer to join a quick conversation with the Product Owner right away. The Product Owner may add it to the Product Backlog and decide whether to adjust for the next Sprint. You do not alter the Sprint Backlog yourself. After the Sprint, the team inspects the pattern of late requests and adapts by adding a buffer for sales demos in future planning.