TECH ENGLISH

Sprint Planning Meetings

Learn the essential English phrases for Agile sprint planning — from estimating story points to negotiating scope and committing to deliverables.

Practice Tech Discussions

Scenario Context

Your team is planning the next two-week sprint. The product manager has brought six user stories. You need to estimate effort, flag a risky dependency on another team's API, and negotiate to descope one story that lacks clear acceptance criteria.

Why This Matters for Engineers

Sprint planning is where commitments are made. If you can't clearly articulate your estimates, raise concerns about scope creep, or explain dependencies, your team may end up overcommitted. Engineers who communicate well during sprint planning are seen as reliable leads. This is especially important in distributed teams where English is the shared language — clarity in planning directly translates to smoother execution.

Essential Phrases

“I'd estimate this at five story points — the API integration adds complexity.”

Giving an estimate

neutral

“Before we commit, can we clarify the acceptance criteria for this story?”

Asking for clarity

formal

“This has a hard dependency on the payments team — we should flag that.”

Raising a dependency

neutral

“I think we're overcommitting. Can we move one story to the backlog?”

Pushing back on scope

neutral

“Could we break this epic down into smaller, deliverable chunks?”

Requesting story splitting

formal

“I can take this one — it's in my area of expertise.”

Volunteering for work

casual

“What's the priority order if we run out of time?”

Clarifying priorities

neutral

“Let's timebox the spike to half a day and reassess.”

Proposing a spike

neutral

“We shipped something similar last quarter — I can reuse that logic.”

Sharing prior work

casual

“I'd like to pair on this with someone who knows the auth module.”

Requesting pairing

neutral

“Given our velocity, this looks like a stretch goal at best.”

Managing expectations

formal

Technical Pronunciation

Word	❌ Common Error	✅ Correct	Tip
Agile	uh-JILE	AJ-ul	Stress on the first syllable, like 'fragile' without the 'fr'.
scrum	skrum	skruhm	Short 'u' sound, like 'drum'.
kanban	KAN-ban	KAHN-bahn	Japanese origin — both syllables have the 'ah' sound.
retrospective	ret-ro-SPECK-tiv	ret-ruh-SPEK-tiv	Four syllables — stress on 'SPEK'.
velocity	veh-LOW-city	vuh-LOSS-uh-tee	Stress on the second syllable: LOSS.

Written vs. Spoken English

Engineers often write one way on Slack or GitHub, but speak differently in meetings. Here's how to translate.

Raising risk

Written (Slack/PR)

There is a dependency risk on the external API delivery timeline.

Spoken (Meeting)

“Heads up — we're blocked until the other team finishes their API, so that's a risk.”

Declining scope

Written (Slack/PR)

I recommend deferring story #4 to the subsequent sprint due to insufficient capacity.

Spoken (Meeting)

“I think we should push story four to next sprint — we don't have the bandwidth.”

Estimating

Written (Slack/PR)

Estimated effort: 5 story points.

Spoken (Meeting)

“I'd put this at about five points.”

Example Dialogue

Product ManagerOkay team, let's look at the six stories I've prepared for this sprint. The top priority is the new checkout flow.

YouBefore we estimate, could we clarify the acceptance criteria for the checkout story? I see it mentions 'support all payment methods' but that's pretty broad.

Product ManagerGood point. Let's scope it to credit card and PayPal for now.

YouThat makes it more manageable. I'd estimate it at eight points — the PayPal integration has some tricky edge cases.

Tech LeadAgreed. What about the inventory sync story?

YouThat one has a hard dependency on the warehouse team's API, which isn't ready yet. I'd suggest we move it to next sprint and pull in the search improvements instead.

Product ManagerThat's fair. Let's do that.

YouAlso, looking at our velocity from the last three sprints, I think we can realistically commit to four stories, not six. Let's prioritize and keep two as stretch goals.

Tech LeadMakes sense. Let's rank them now.

Common Questions

How do I push back when the product manager wants too many stories in a sprint?

Use data: reference your team's average velocity from recent sprints. Say something like, 'Based on our velocity of 30 points, committing to 45 points would be risky. Can we prioritize and keep some as stretch goals?' This keeps the conversation objective rather than emotional.

What's the difference between a spike and a story?

A spike is a time-boxed research task to reduce uncertainty — you're investigating, not building. A story delivers shippable value. In spoken English, you'd say: 'Let's timebox a spike for half a day to figure out the right approach, then we'll write the actual story.'

How do I explain a dependency to non-technical stakeholders?

Use a simple analogy: 'We can't build the roof until the walls are up. The payments team's API is our wall — once it's ready, we can move fast on our part.' Avoid jargon like 'upstream dependency' when talking to non-engineers.

Stop Stumbling on Tech Calls

Practice explaining code, architecture, and bugs with an AI coach that understands engineering context.

Start Practicing Now

No credit card required.

More Tech Scenarios

Daily Standup Updates

System Design Discussions

Giving Demo Presentations