Sprint Planning phrases in English
Sprint planning decides what the team commits to for the next two weeks. The hard part is saying a number, asking what an estimate includes, and pushing back when the plan is bigger than the team. These phrases help with each. Fill in the “…” with your own ticket, name or date.
Goal and capacity
-
1
What's the sprint goal we're committing to?
Before anyone picks tickets.
-
2
I'm off on …, so I have about … days this sprint.
Telling the team your capacity up front.
-
3
Our capacity is around … points, with … out.
Setting the limit before the list grows.
-
4
Let's agree on the goal first, then pick the tickets.
When the meeting starts with a list instead of a goal.
Estimating
-
5
I'd put this at … points, because …
A number with a reason is easier to agree on.
-
6
That feels high to me. What's driving it?
Questioning an estimate without dismissing it.
-
7
Does that estimate include testing and code review?
The question that catches most low estimates.
-
8
There are a lot of unknowns here. Can we spike it first?
When nobody can size it honestly yet.
-
9
I can't estimate this until we know …
Naming the missing piece.
-
10
It's similar to …, which took us …
Estimating from past work.
-
11
Can we split this into two tickets: … now, … later?
When a ticket is too big for one sprint.
Scope and trade-offs
-
12
If … goes in, something has to come out.
When the plan is over capacity.
-
13
We're over capacity by about … points.
Putting the problem in numbers.
-
14
Which of these matters more to the sprint goal?
Asking the product owner to choose.
-
15
Could we ship a smaller version first: …?
Offering a cut instead of a no.
-
16
I'd rather commit to less and finish it.
Arguing for a realistic plan.
-
17
Can we move … to next sprint?
Proposing what comes out.
Clarifying
-
18
What's the definition of done for this?
Before you commit to a ticket.
-
19
Who's the owner on this one?
When a ticket touches several people.
-
20
Are the designs final, or still changing?
Checking a risk before estimating.
-
21
What does … depend on?
Finding the order of the work.
-
22
Just to confirm: we're committing to …, … and …
Closing the meeting with the list said out loud.
Common mistakes
Sentences non-native speakers often say in a sprint planning, and a more natural way to say them.
-
You said This task is very easy, 1 point.
Better This one looks small, maybe a point, unless the API needs changes.
Give the assumption, so others can tell you if it's wrong.
-
You said I think it cannot finish in this sprint.
Better I don't think we can finish it this sprint.
Put the not on think, and the team or a person as the subject.
-
You said Please give me more time.
Better I'd need about two more days for this.
Ask for a number of days, not time in general.
-
You said We should discuss about the API first.
Better We should discuss the API first.
Discuss takes no about.
-
You said Do you understand my idea?
Better Does that make sense?
Do you understand can sound like you doubt the listener.