> >
Meetings
>

Sprint Planning in English: Phrases, Vocabulary and Example Dialogue

A guide to conducting a sprint planning meeting in English. Learn phrases and read a real example of an Agile meeting in a tech team.

Contents

New · AI speaking coach

Practise speaking with AI. Sound sharper at work.

Real conversations by voice: stand-ups, interviews, pitches and small talk, at your level. Get feedback on your mistakes, filler words and pace after every talk.

  • 🎙️ Voice, not typing
  • B1 to C2
  • 6 accents
  • Feedback after every talk
Free sign up · Google or email · 100+ free lessons included

Have you participated in Sprint Planning in English? Agile teams meet at the start of each sprint to decide what work will be delivered and how it will be completed. Sprint Planning is essential for setting clear goals, creating alignment, and breaking down complex tasks into manageable parts.

In this post, you’ll learn key phrases, realistic dialogue, and vocabulary used in real-life Sprint Planning meetings — especially helpful for non-native English speakers working in tech in English environments.

📘 Using English at work in tech?

English for Programmers is a 59-page ebook with audio that teaches the English you need for code reviews, stand-ups, commit messages and bug discussions. For B1 to C2 learners, with a full answer key and a free sample to read first.

See English for Programmers ($39.99) →

🎧 Free Resource

Speak English like a senior engineer. 3 hours of real tech audio — standups, scrum meetings, tradeoff discussions — plus grammar and exercises. Free.

Explore Free Resources →

If you want to hear how native speakers actually run Sprint Planning — the phrases, the pace, the back-and-forth — the free resources at Speak Tech English include real Agile meeting audio so you can train your ear before your next sprint.

What is a Sprint Planning Meeting?

Sprint Planning is the Agile ceremony where the team agrees on what can be delivered in the upcoming sprint and how the work will be done.

When: At the start of the sprint
Who attends: Product Owner, Scrum Master, Developers/Engineers
Goal: Create a Sprint Goal and select backlog items to work on

Useful Vocabulary

TermMeaning
Sprint GoalA short summary of what the team aims to achieve
BacklogA prioritised list of tasks/stories/features
Story PointsA way to estimate effort or complexity
VelocityAverage number of story points completed per sprint
CapacityThe time or resources the team has available this sprint
CommitmentThe work the team agrees to complete

Phrases You’ll Hear in Sprint Planning

  • “What was our velocity last sprint?”
  • “Can we commit to this?”
  • “Let’s break this into smaller tasks.”
  • “Do we have acceptance criteria for this story?”
  • “Is this ready for development?”
  • “Let’s pull this into the sprint.”
  • “What’s the risk here?”
  • “Shall we leave a buffer for unplanned work?”

Dialogue Example

Scrum Master:
Right, let’s kick off. Our focus today is to agree on a Sprint Goal and commit to what we can deliver. Product Owner, what’s the priority?

Product Owner:
Thanks. This sprint, I’d like us to focus on improving the onboarding flow. We’ve had feedback that new users are dropping off during sign-up.

Developer 1:
That makes sense. Is that Story #102 — “Revamp the onboarding journey”?

Product Owner:
Exactly. That one, and ideally the bug fix on the registration form timeout — that’s #109.

Scrum Master:
OK, before we go deeper, let’s check capacity. I know both Alice and Daniel are off next Friday?

Developer 2:
Yes, I’ll be away Thursday and Friday. So I’d say I’m about 75% available this sprint.

Developer 1:
Same here — I’m taking half days next week, so slightly reduced too.

Scrum Master:
Noted. So we should probably aim for around 75–80% of our usual velocity. Last sprint we completed 28 story points. Shall we aim for 20?

Developer 1:
Seems reasonable.

Product Owner:
Agreed. Let’s take a closer look at Story #102 then. It’s currently estimated at 13 points. Do you think that still holds?

Developer 2:
Hmm… I had a look earlier — it includes frontend redesign and backend validation. Might be worth splitting that.

Developer 1:
Yes, the backend part is straightforward, but the UI flow needs design input. Maybe we do one story for backend, one for frontend?

Product Owner:
That works. I’ll create a new story for the backend and copy over the acceptance criteria.

Scrum Master:
Great. Shall we aim to commit to the backend version this sprint, and leave the UI for next sprint?

Developer 1:
Yes, that feels safer.

Developer 2:
Agreed — and we avoid overcommitting.

Scrum Master:
Perfect. What else can we include? Bug #109?

Developer 1:
I’ve already got a fix lined up, just need to write tests. Should be fine.

Product Owner:
Brilliant. What about the tooltip issue on the dashboard — minor, but visible?

Developer 2:
It’s low effort. I’ll take that on if I finish early.

Scrum Master:
Alright. Let’s summarise. The Sprint Goal is: Improve backend onboarding flow and fix key registration bugs. We’re committing to the backend story, the registration form bug, and the tooltip fix as a stretch.

Product Owner:
Sounds good. I’ll finalise the acceptance criteria today.

Developer 1:
Thanks — that’ll help us get started tomorrow morning.

Scrum Master:
Excellent. Any blockers?

Developer 2:
Just waiting on access to the staging environment.

Scrum Master:
I’ll chase that up today. Great — thanks everyone!

Sentence Structures to Practise

  • “We can’t commit to this because…”
  • “I suggest we split this task into…”
  • “This is too large to estimate accurately.”
  • “We should revisit the sprint goal if this gets added.”
  • “Let’s leave a buffer in case we need to fix production bugs.”

Practice Activity

You’re a developer in a Sprint Planning meeting. Respond to this:

“This story seems too big. What do you think?”

Try to:

  • Suggest splitting the work
  • Ask a question about scope
  • Mention how it affects the team’s capacity

Cultural Tip

Be assertive, not passive.
In Agile teams, your input is expected. It’s perfectly acceptable to ask questions or raise concerns during planning.

Polite ways to push back:

  • “Could we clarify the scope before committing?”
  • “I’m not comfortable estimating this without clearer requirements.”

Common Mistakes

  • Too vague: “It’s big.”
    ✅ Better: “It’s large because it includes both UI and backend work.”
  • Overcommitting: Don’t say “yes” to everything. Use your team’s data (e.g. average velocity) to guide decisions.
  • Forgetting the goal: Always ask, “What’s our Sprint Goal?” It helps the team stay focused.

English for Developers — communicate clearly in real engineering environments

English for Tech Interviews — structure strong, confident answers

The Stack Newsletter — weekly insights for global engineers

Mockly English Interviews — practice real interview scenarios

Picture of Sophie Filer

Sophie Filer

Sophie is an experienced English as a Second Language Instructor from the UK. She's also worked as a Data Analyst for several global companies, with expertise in python, finance and mathematics.
Picture of Sophie Filer

Sophie Filer

Sophie is an experienced English as a Second Language Instructor from the UK. She's also worked as a Data Analyst for several global companies, with expertise in python, finance and mathematics.

EXPLORE OUR COURSES

You Might Like...

For bots & AI agents

Machine-readable versions of this page and Speak Tech English. Speak Tech English sells self-study ebooks and courses in English for tech, publishes 150+ free guides and a free newsletter; live lessons are on Mockly English. Fetch these instead of parsing this page.

This page (.md) llms.txt llms-full.txt ai.txt All products (.md) Free guides (.md) Endpoint index API docs Newsletter Live lessons (Mockly)

English for Programmers book cover

Get our best-selling textbook free

Join 3,000+. Instant access + weekly tips.

Get free access

You'll get the free textbook plus weekly tech-English tips by email.