Standups are short daily meetings where a team checks it is still on track and flags anything in the way. Done well, one takes 15 minutes and clears blockers before they cost a day.
Done badly, a standup becomes the longest, least useful meeting of the week.
What a standup is for
A standup answers one question each day: is the team on track, and if not, what's in the way? Its job is to spot problems early. Solving them happens afterwards, and reporting to a manager isn't part of it.
The name comes from the habit of holding it on your feet. Standing gets uncomfortable after a few minutes, which nudges everyone to keep it short. Plenty of remote teams now meet on a video call, sitting down, and the principle survives: if it would be uncomfortable to keep going, it has gone on too long.
Most teams meet at the same time every working day, often first thing, so the plan for the day is fresh. In Scrum it has a formal name, the Daily Scrum, and the Scrum Guide caps it at 15 minutes.
The three questions
The classic format has each person answer three questions in turn:
- What did I finish yesterday?
- What am I working on today?
- Is anything blocking me?
The third matters most. A blocker is anything stopping you making progress: a failing build you can't fix, a pull request waiting for review, an unanswered question about what a feature should do, missing access to a server. Saying it out loud in front of the whole team means the person who can unblock you hears it the same morning rather than days later.
The first two give context. They let the team notice overlaps ('I'm touching the login page too') and gaps ('nobody has picked up the payment bug').
A worked example
Picture a four-person team building a checkout page. Their standup might go like this:
Wondering how this was made? How we make these