The Sprint Planning Negotiation

Scene: It is Monday morning and your team is planning the next two-week sprint. Marco, the product manager, has brought seven items and assumes all of them will fit. You know the team can realistically finish four. Your job in the next half hour is not to say no; it is to make the trade-off visible, so that Marco decides what to cut with you rather than against you.

Marco: So that is the list — seven stories, all of them already promised to the customer. Can the team take it? You: Before I answer, let me put our capacity on the table. We have eight working days after the holiday, and two engineers are on call. Historically that gives us about four stories of this size. So the honest answer is: not all seven.

Marco: That is a problem. Sales already told the client the export feature ships this month. You: Then let's protect the export feature and build the sprint around it. What I want to avoid is committing to all seven, missing four of them, and having you find out on day nine. I would rather we decide together today which three slip.

Marco: I hear you, but I am not comfortable dropping the audit log. Compliance has started to push back on us, and I cannot keep stalling them. You: Fair. Let's lock export and the audit log as must-haves, then. That leaves room for two more. Of the remaining five, which one would hurt the least if it moved to the next sprint?

Marco: The dark mode work and the two dashboard tweaks can wait, I think. The onboarding email is the one I would fight for. You: Then here is what I will commit to: export, the audit log, the onboarding email, plus one dashboard tweak if we clear the first three by Thursday. Everything else is explicitly out of scope this sprint.

Marco: Can you at least start the dark mode work if there is time? You: I can put it at the top of the stretch list, but I do not want to call it a commitment. If I pad the sprint with maybes, the number stops meaning anything and you lose the ability to plan around it. A short list we actually hit is worth more to you than a long list we miss.

Marco: That is reasonable. Send me the final scope so I can reset expectations with sales. You: I will write it up this afternoon: four committed items, one stretch item, three deferred with the reason next to each. If anything blows up mid-sprint, I will flag it the same day rather than at the review. No surprises.

Notice what you never did. You never said the word impossible, and you never argued about whether Marco's requests were reasonable. You brought capacity as a fact, asked him to rank his own list, wrote the cut items down instead of letting them quietly vanish, and refused to disguise a hope as a commitment. Scope negotiations go badly when they become a contest of will; they go well when both sides are staring at the same constraint.