Quick answers
- What is a daily standup?
- A short team meeting where each person shares what they did, what they'll do, and any blockers.
- How long is a standup?
- Usually 15 minutes or less. Each person speaks for 30–60 seconds.
- What are the three standup questions?
- What did I do yesterday? What will I do today? Are there any blockers?
- What if I'm blocked?
- Say it clearly: "I'm blocked on [X] because [Y]." The team can then help or escalate.
What it is
Daily standups (or daily scrums) are a core agile ritual. Each person typically answers three questions: What did I do yesterday? What will I do today? Are there any blockers? The meeting is kept short—usually 15 minutes or less—and is meant to align the team, not to solve problems.
Why it matters
Standups surface blockers early, keep everyone informed, and create accountability. Clear, concise updates help the team move faster. Non-native speakers often struggle with filler words, unclear status, or failing to highlight blockers—practice helps you sound confident and get the support you need.
Instead of → Say
| Instead of | Say |
|---|---|
| I did some stuff | I completed the login API integration |
| I'm working on it | I'm halfway through the payment flow |
| I have a problem | I'm blocked on the deployment—CI is failing |
| Same as before | I'm continuing with the refactor I mentioned yesterday |
| Almost done | I have one test left—should finish by EOD |
Example dialogue
Manager: Sarah, what did you work on yesterday?
Sarah: I finished the API integration for the checkout flow. All tests are passing.
Manager: And today?
Sarah: I'm starting on the Stripe webhook handler. I'll also review the two PRs in the queue.
Manager: Any blockers?
Sarah: No blockers right now. I'll reach out if the Stripe docs don't cover our edge case.
Common mistakes
- Giving vague updates like "I worked on the feature" instead of naming the specific task
- Going into deep technical detail—standups are for alignment, not problem-solving
- Skipping blockers or downplaying them
- Rambling—keep each answer to one or two sentences
- Not listening to others' updates
Frequently asked questions
- How long should my standup update take?
- Aim for 30–60 seconds per person. Name the task, the status, and any blockers. Avoid diving into solutions—save that for after the standup.
- What if I have nothing new to report?
- Say something like: "I'm continuing with [task from yesterday]. No blockers." It's okay to have overlap—the team needs to know you're still on track.
- Should I mention small tasks?
- Focus on what helps the team understand your progress. Small tasks can be grouped: "I did some bug fixes and code review."
- How do I say I'm blocked without sounding negative?
- Be direct: "I'm blocked on X because of Y. I've tried Z." Stating the blocker clearly helps the team help you.
- Can I ask questions during standup?
- Brief questions are fine. For longer discussions, say "Let's take this offline" and schedule a follow-up.
Ready to practice?
Try this scenario with AI and get feedback on your communication.
Start practicing