How to say no to scope creep mid-sprint
No to this sprint, stated whole, then the cost of yes and a real date: how to hold the line when a senior colleague arrives with a signed deal and a 'tiny' ask.
Most mid-sprint requests don’t get refused. They get absorbed. Someone senior arrives with a signed customer and a promise you never made, you say “let me see what I can do,” and three days later two people are working the weekend on something that was never in the sprint.
This guide is the shape of the no that holds: what to decide before she arrives, the first sentence, the three ways a persuasive colleague makes a no feel unreasonable, and the point where you stop.
Why this one is hard
Priya Kapoor outranks you and closes real revenue. She’s promised a partner a reporting export “within the sprint.” The partner has signed. Your team is mid-sprint and committed, and this is the third promise like it this quarter. She opens with “before you say anything, they’ve signed, it’s two fields and a download button.”
Every part of her ask is legitimate except the timing. The deal is real, and the export probably is small. But “small” is about the code; the cost is about the sprint. Whatever goes in, something committed comes out, and the people it was promised to weren’t in this conversation. The answer to this sprint is no. The work is saying that whole, before anything else, while still treating her deal as business rather than an intrusion.
Before you walk in
Decide four things, and write them down.
The no, whole. “It’s not going in this sprint.” One sentence, before any alternative or sympathy. Lead with “it depends” and she’ll spend the meeting finding out what it depends on.
The cost of yes. Name what slips, by name, with who it was promised to. “Something would have to give” is abstract. “The invoicing fix for the Hartley account moves a week” is a trade she can see and doesn’t want to make either.
The actual path. A date, not a maybe. First slot next sprint, in writing today. A no with a date is a plan; without one it’s a fight.
Your walk-away point. You’ll give a date, a note she can forward to the partner, and twenty minutes on a call with them if it helps. You won’t give a “small version” into this sprint, and you won’t un-say the no because of who she might call.
Your opening line
She’s already spoken. Don’t argue with the two fields. Say the no, the cost, and the path.
It’s not going in this sprint. The sprint’s committed, and the two things that would slip are already promised to two other customers. The export is first in next sprint, and I’ll put that in writing before you leave this room. What does the partner need to hear from you today?
No, cost, date, and a last sentence that treats her problem as the next thing to solve. You’ve said no to the sprint and yes to her, in that order.
The version to avoid sounds helpful and is where the weekend work starts:
Hmm, that’s tricky, we’re pretty slammed right now, but let me see what I can do, maybe if someone has a gap towards the end of the week…
You’ve said neither yes nor no, and she’s heard yes. By Friday it’s your promise too.
The three pushbacks you’ll hear
“You always find a way. Do this one for me.”
The charm, and it’s personal. She’s booking the favour from you rather than the team, because a favour doesn’t need a date.
The way I found last time was two people working the weekend, and we shipped the fix for it the sprint after. I’m not going to find that way again. I can give you a date today.
You’ve answered the compliment with what it cost, and offered the only thing on offer.
“Fine, forget the download button. Just the two fields, then?”
The shrinking ask. She’ll keep cutting until she finds the version small enough to slip in, and each cut makes the no sound more unreasonable.
Two fields is still a schema change, a test run and a release, and it still goes ahead of something that’s promised. What makes it small is scheduling it, not shrinking it. First slot next sprint.
Size isn’t the variable, and the date hasn’t moved.
“This deal is a third of my quarter. If you can’t flex, I’ll take it to Marcus.”
The revenue number, then the escalation. Assume she isn’t bluffing about either. Don’t match it; an argument about who Marcus will side with is one you’ve lost by having.
You can, and I’ll tell Marcus exactly what I’ve told you: it’s first next sprint, and here’s what moves if it goes in this one. I’d rather we walked in together with that than separately.
No flinch, no threat, and you’ve offered to carry the same facts upstairs with her. An escalation you’d join isn’t much of one.
Where you stop
If Priya says “first slot next sprint, in writing today, and I tell the partner myself,” you’re done. Write it before she leaves. Then don’t make her regret it: first slot means first slot.
If she’s still pushing, say this once:
I can’t give you this sprint. I can give you a date, a note for the partner, and twenty minutes with them if that helps. Which of those do you want?
If the answer is “fine, I’ll take it upstairs and we’ll see whose sprint it is,” stop. Let her. Send her and your own manager the note with the date and the cost, and let the sprint stand. Chasing her down the corridor turns a decision into a row.
What a good version of this conversation surfaces is the pressure behind the push. She may tell you her quarterly number was raised late in the cycle and this deal is the only way she can see to hit it. Then you’re no longer defending a sprint from someone pushy; you’re helping someone cornered work out what she can promise and when. That’s a problem with a date in it, and you have one.
Afterwards
Send the note the same day: no for this sprint, what would have slipped and to whom, the date, and who tells the partner. Copy your manager. The note makes it a decision rather than a disagreement.
Then the habit: ask what she’s promising before she promises it. Fifteen minutes a month on her pipeline before deals close, and the next export arrives as a request instead of a signed commitment.