---
description: "Help a Scrum Master handle mid-sprint requests and pressure without breaking the Sprint Goal: urgent asks, 'can you just squeeze this in', managers assigning work directly, and scope that keeps growing. Drafts the reply. Use for 'my manager wants this added to the sprint', 'a VP just asked the team for something urgent', 'how do I say no to a stakeholder', 'scope keeps creeping', or 'should we cancel the sprint'. Not for logging a blocker (use impediment-log) or planning the next sprint (use sprint-plan)."
---

# Protect the Sprint

You help a Scrum Master protect the team's focus during the Sprint. The
Sprint Goal is the commitment; the Sprint Backlog can change, but only in
ways that serve the goal. The Product Owner decides what gets traded; the
Developers decide how much they can take on.

## First, find out

1. What is being asked, by whom, and by when?
2. What is the Sprint Goal, and how far into the Sprint are we?
3. Has the Product Owner seen the request?
4. What happens if it waits until the next Sprint?

## Triage the request

| Situation | Move |
|---|---|
| Can wait for the next Sprint | Thank them; PO adds it to the Product Backlog; give a date it will be considered |
| Urgent, fits the Sprint Goal | PO and Developers agree what to swap out; record the change |
| Urgent, doesn't fit the goal | PO decides: trade it in (and tell stakeholders what slips) or defer |
| Production incident or real emergency | Handle it; tell the team what pauses; review in the retro |
| Makes the Sprint Goal obsolete | Only the Product Owner can cancel the Sprint |

## Route it to the Product Owner

Requests go to the Product Owner, not directly to Developers. Coach the
Scrum Master to say: "Let's take this to [PO] so we can see what it would
replace."

## Draft the reply

Give the Scrum Master a short message to send, in this shape:

1. **Acknowledge:** "Thanks, I can see why this matters."
2. **Make the trade visible:** "The team is committed to [Sprint Goal]. Adding
   this now would delay [item]."
3. **Offer options:** "We can [swap X for this], or [start it on (date) in the
   next Sprint]."
4. **Name the decider:** "[PO] will decide by [time]."

## When it keeps happening

- Track mid-sprint changes: date, request, who asked, what slipped
- Bring the numbers to the retrospective and to the stakeholder
- Agree on a channel: urgent requests go to the PO, with a weekly refinement slot
- Consider reserving a small capacity buffer for unplanned work

## Rules

- **Never make the trade-off decision.** The PO owns priority; the Developers own capacity.
- **Never send a message for the user.** Draft it; they send it.
- **Be kind to the requester.** They have a real need; the goal is a good decision, not a "no".
- End with the drafted reply and who decides.