Quick answers
- What is sprint planning?
- A meeting where the team commits to work for the next sprint and aligns on goals.
- How do I commit to work in sprint planning?
- State what you can deliver, any dependencies, and raise concerns about capacity or scope.
- What if I can't take more work?
- Be direct: "I'm at capacity. I can take [X] but not [Y]."
What it is
In sprint planning, the team reviews the backlog, estimates work, and commits to sprint goals. Each person says what they can realistically deliver and raises concerns about capacity or dependencies.
Why it matters
Clear communication in sprint planning prevents overcommitment and missed expectations. Saying "I can take this story" or "I need two more days for the migration" helps the team plan realistically.
Instead of → Say
| Instead of | Say |
|---|---|
| I'll try to do it | I can commit to this story. I'll need the API schema by Wednesday. |
| It's too much | Given the support work, I can take three stories max this sprint. |
| I don't know | I need to spike the integration first—I'll have an estimate by tomorrow. |
| Put it on me | I can own the payment flow. I'll need design review by mid-sprint. |
| That's not possible | The migration blocks that. I'd suggest we prioritize the migration first. |
Example dialogue
Scrum Master: Can you take the auth refactor this sprint?
You: I can take it, but it depends on the security review. If that lands by Tuesday, I'll have it done by Friday.
Scrum Master: What if it's delayed?
You: Then I'd drop the optional cleanup task and focus on the refactor. I can pick up the cleanup next sprint.
Scrum Master: Sounds good. Anything else?
You: I'm on call next week, so I'll build in buffer for incidents.
Common mistakes
- Overcommitting to avoid saying no
- Not raising dependencies or blockers
- Staying silent when you disagree with scope
- Giving vague estimates—"a few days" instead of "three days"
- Not accounting for meetings, support, or on-call
Frequently asked questions
- How do I say I can't take more work?
- Be clear: "I'm at capacity with [current work]. I can take [X] more stories, but not [Y]."
- What if I'm unsure about an estimate?
- Say so: "I need to spike this first. I'll give a better estimate by [date]."
- How do I raise a dependency?
- "I can do this, but it depends on [X] from [team/person]. If that's done by [date], I'm good."
- Should I negotiate scope?
- Yes. If scope is too big: "We could split this into two stories and do the first this sprint."
- What if I disagree with the sprint goal?
- Share your view: "I'm concerned about [X]. Would it make sense to [alternative]?"
Ready to practice?
Start practicing with our available scenarios and get instant feedback.
Start practicing