Home → Part 05
Daily Standup: Synchronization, Not a Status Report
We stand in a circle and take turns presenting our homework. Who cares? There is only one question that matters: are we going to make the goal, or are we sinking?
- If what you did yesterday does not affect today, it does not matter. Tell me what is blocking you.
- 15 minutes is a ceiling, not a target. A mature team takes 6–7.
- Walk the board right to left. Go item by item, not person by person, so the focus stays on the sprint goal.
- Do not wait for the daily to raise a blocker. The daily is a safety net, not the only emergency line.
Purpose: a single question
The daily exists to answer one question: are we on track for the sprint goal? Under it sit three jobs:
- Check progress. Is work flowing towards Done? Are we ahead or behind?
- Surface impediments. What stopped, and who will unblock it?
- Align the day. Who is on what, and where is collaboration needed?
None of those three require an answer to "what did you do yesterday". That is the flaw in the classic three-question format: it looks backwards, when the meeting exists to plan today.
A better format: walk the board right to left
Instead of going person by person, go item by item and start with the ones closest to Done. The reason is simple: the work nearest to delivering value has the highest priority. Starting new work is worth less than finishing work that is nearly finished.
- Done. Briefly confirm what completed. Does it meet the Definition of Done?
- In review / testing. Who is looking at it, what is blocking the move to Done?
- In progress. What does this need to move today?
- To do. Is the next item clear, and who is pulling it?
One question per item is enough: "What is the next action to move this forward?" If that question cannot be answered, the item is not actually moving.
The wall of shame: common anti-patterns
1. Jira bingo
"Yesterday I did SC-144, today I will do SC-148."
Nobody memorises ticket numbers. Say which capability you moved and how it relates to the goal: "I finished validation on the payment form, today I am on the 3D Secure callback."
2. The zombie task
"Still working on SC-145" — day one, day two, day three.
The culprit here is not the person speaking but the team's silence. If someone has been stuck on the same item for three days and nobody asks "do you need help, we are going to miss the goal", you are not a team — you are people sitting next to each other.
My own rule: any item still in the same state at the end of the second day gets discussed automatically; nobody has to work up the courage to ask. Making it a rule in advance takes the personal edge off the question.
3. "Who cares" updates
"I had my year-end review meeting with HR." — If it is not on the board and does not affect the sprint goal, it is not daily material. That sounds harsh, but unrelated chatter kills attention: people stop listening, and once they stop listening they stop noticing blockers.
The parking lot rule
If a topic takes more than three sentences, or turns into analysis ("well, if we change that API then the consumer..."), stop it:
End the daily at the stated time. Then the two or three relevant people stay and solve it; everyone else goes back to work. A discussion five people have to sit through is a problem two people could have solved.
The compass: the burndown chart
Look at the chart mid-sprint. It speaks from the board, not from feelings.
If the trend says you will not make it, say so now. Two options: negotiate with the PO immediately ("let us drop X or narrow the scope") or the team decides to pull it back. Either way, share the risk.
Early bad news is a risk; bad news on the last day is a failure.
If things are going better than expected, do not hide it. Tell the PO: "we have capacity, shall we pull the next item?"
The long-term benefit: the PO stops trying to stuff the sprint, because they know you will ask for more work if you finish early. That removes the tension from planning.
The chart only tells the truth if the Definition of Done is solid. In ours, Done means: tests pass, CI/CD has deployed to the relevant environment, and the feature has been verified working there.
If an item is moved to Done because the code runs locally, the chart drops but the work is not finished. That is the illusion of progress, and the bill arrives in the last two days of the sprint.
The Product Owner: guest or police?
Attendance is optional. The daily is where the development team aligns with itself, and in practice the PO is that team's customer. Where trust is high there is no need for them to be present; they know they will be told if the burndown turns red or a blocker appears.
If the PO does attend, the rule is: observe, do not steer. The moment the PO starts talking, the meeting changes direction and the team begins reporting to them instead of to each other.
The 30-minute anti-pattern: a diagnosis table
| Symptom | Likely cause | Fix |
|---|---|---|
| Long individual updates | Status reporting culture | Switch to a board-driven format |
| Problem solving in the meeting | No clear "offline" rule | Facilitator enforces the parking lot |
| Too many attendees | Team too large or wrong people | Split the team or limit to the core |
| Waiting for latecomers | No start discipline | Start on time, always |
The alternative: kill the meeting (async daily)
Do we really need to meet at the same time every day? No. For mature teams, especially those spread across time zones, the synchronous daily is an outdated assumption.
- Format: a bot asks three questions — what did you finish, what are you pulling next, are you blocked?
- Benefit: no context switch, no waiting for the mic, no broken deep work.
- Condition: the team must actually read it. If nobody reads it, go back to synchronous.
My own metric: after switching to async, track for two weeks how many hours pass between a blocker being posted and someone responding. If that number goes above four hours, async is not working for that team. Let the decision rest on the number, not on a feeling.
Getting stuck at 2pm and waiting for tomorrow morning's daily to say "I am stuck". If you are drowning, say so now. The daily is a safety net, not the only emergency line.
Checklist
- Is the board open and shared on screen?
- Are we walking right to left, or person by person?
- Was every item stuck for more than two days discussed?
- Was the long discussion parked for later?
- Did it end at the stated time?
- Does every raised blocker have an owner?
Conclusion
The daily is the heartbeat of the process. If it beats irregularly — long, dull, status driven — the team is sick. The cure is simple: stop reporting to a manager and start talking to each other. The question is the same every morning: what are we doing to win today?
Walking the board right to left, the parking lot rule, the anti-pattern names and the async approach are adapted from İbrahim Demir's Daily Standup post and his Async Daily Standup post. The two-day automatic discussion rule and the blocker response-time metric are my additions.