How should the team handle a PO adding urgent work mid-sprint?

WHAT THIS TESTS: This tests whether you understand the empirical pillars of transparency, inspection, and adaptation, and how the Scrum Team uses them to manage work within a Sprint. It also tests whether you know that the Product Owner orders the Product Backlog while the Scrum Team turns a selection of the work into an Increment during the Sprint, and that the Scrum Master fosters an environment where these accountabilities are respected.

A GOOD ANSWER COVERS: A good answer hits four things in order. First, the team makes the emergent process and work visible so that the Product Owner can see the impact of new requests on the current selection of work. Second, the Scrum Team and the Product Owner inspect the progress toward agreed goals frequently and diligently to detect undesirable variances caused by the added work. Third, the team uses adaptation to adjust if the process deviates outside acceptable limits, which means renegotiating the selection of work for the Sprint rather than simply absorbing every new item. Fourth, the Scrum Master facilitates this conversation by fostering an environment where the team can make decisions based on what is observed, ensuring that inspection leads to adaptation rather than blame.

COMMON WRONG ANSWERS: A red flag is suggesting the team should refuse to talk to the Product Owner or escalate to management outside the Scrum Team. Another red flag is proposing that the team work extra hours to fit the new work, which ignores lean thinking and the focus on reducing waste. A third red flag is saying the Product Owner can add work whenever they want because they order the backlog, which misses the distinction between ordering the Product Backlog and managing the selection of work inside the Sprint.

LIKELY FOLLOW-UPS: An interviewer might ask how you would measure whether the process has deviated outside acceptable limits. They might also ask what you would do if the Product Owner insists the new work is more valuable than the current selection. Another follow-up could be how the five Scrum events provide cadence for this inspection.

ONE CONCRETE EXAMPLE: Imagine a two-week Sprint where the Product Owner adds three urgent items in week two. The Developers invite the Product Owner to inspect the current Increment and the progress toward agreed goals. They make transparent that adding all three items would require dropping two existing items to avoid deviation from sustainable pace. The Product Owner agrees to swap one item and defer the others to the next Sprint. The Scrum Master facilitates this discussion during the Sprint, ensuring the team applies empiricism rather than reacting emotionally.