What to say in standup: the standup meeting agenda, with examples for engineers

The standup meeting agenda

Most daily standups follow the same simple agenda, based on three classic questions that each person answers in turn:

1. What did you do since the last standup?
2. What will you do next?
3. Is anything blocking you?

Some teams walk the board instead: they go through the tickets in progress, right to left, and whoever owns each one speaks to it. Others add a short slot at the end for announcements or for agreeing who needs to talk afterwards. Whatever the format, the purpose is the same: help the team see where the work is and spot problems early. It's a planning meeting, not a performance review.

That purpose tells you what to say. Your update is useful when it helps someone else make a decision: whether to review your pull request today, whether the release is on track, whether they should help you. Everything else is optional.

What a good standup update sounds like

A good update is short, specific and ends clearly. Aim for around thirty seconds to a minute. It names the work in terms the team recognises (the ticket, the feature, the bug) and says where it stands, not how hard it was.

The clear version has the same facts, minus the story. It tells the team three things they can act on: the cause is known, a fix is coming, and there's a review to expect around lunchtime.

A simple template

If you'd like a pattern to lean on: "Yesterday I [finished / got to] X. Today I'm doing Y. [Blocker, or: no blockers.]" Then stop. You'll vary it naturally once it's a habit, but it's a reliable fallback when your mind goes blank.

What to say in standup: examples for awkward days

When you're blocked

Being blocked is exactly what standup is for, so say it plainly and say what you need. Name the person or team if you can.

Note the last sentence: saying what you'll do while you wait shows you're not stuck in place.

When you have nothing to show

Some days the work doesn't move, or it moves in ways that don't look like progress: reading code, debugging, failing to reproduce a bug. Don't pad it and don't apologise. Say what you learnt, because learning is progress.

When something went wrong

If you broke the build or a deploy went badly, lead with it. People will find out anyway, and hearing it from you, with what you're doing about it, builds trust.

When your update is just "same as yesterday"

Long tasks make for repetitive updates. Add one new detail each day so the team can see movement: a percentage of tests passing, the step you've reached, or the date you now expect it to be done. "Still on the migration. All tables but two are moved, and I expect to finish on Wednesday."

Daily standup questions you might get asked

Even in a short meeting, people ask follow-ups. These come up a lot, so it's worth having a one-sentence answer ready:

• "When will it be done?" Give your best estimate and your confidence: "Thursday, if the review goes smoothly."
• "Do you need help?" Say yes when it's true. Asking early is a skill, not a weakness.
• "Is this still on track for the release?" Answer yes or no first, then the reason.
• "Can we take that offline?" That's a polite signal that the detail belongs after the meeting. Agree, and name who you'll talk to.

If those questions throw you, practise them before the meeting. That's one of the meetings we built Staging Mind for: you write a short brief about your week, and three AI colleagues question you about it out loud, with a clock running, the way a real standup would.

Small habits that make standup easier

• Write your update before the meeting. Three short lines in a note take two minutes and remove most of the stress.
• Lead with the headline. Start with the most important fact: done, blocked, or at risk.
• Keep detail for afterwards. If a topic needs more than a minute, suggest a follow-up with the people who need it.
• Listen to the others. Standup is also for learning what your teammates need. An offer of help after the meeting goes a long way.
• End clearly. "That's it from me" hands over cleanly and stops you trailing off.

Frequently asked questions

What are the three standup questions?

What did you do since the last standup? What will you do next? Is anything blocking you? Many teams use these three questions as their whole standup meeting agenda.

How long should a standup update be?

Around thirty seconds to a minute for each person is a good target. If a topic needs longer, mention it briefly and discuss it after the meeting with the people involved.

What should I say in standup if I did nothing?

Say what you learnt or ruled out, what you'll try next and whether you need help. Investigation and debugging are real work, even when there's no pull request to show for them yet.

Should I mention blockers even if they're small?

Yes, briefly. Standup exists to surface blockers early. Name the blocker, say what you need and from whom, and say what you'll work on while you wait.