The Daily Standup is a fifteen-minute meeting held every day in which each team member answers three questions — What did you do yesterday? What will you do today? Are there any blockers? — standing up, so that the physical discomfort of standing encourages brevity, a mechanism that has never once worked.
The standup was invented to replace the status meeting. The status meeting was a one-hour weekly event in which each person reported to the manager what they were working on. The standup is a fifteen-minute daily event in which each person reports to the Scrum Master what they are working on. The innovation is the frequency, the posture, and the vocabulary. The content is identical.
The three questions are designed to surface blockers — impediments that prevent work from progressing. In practice, the three questions surface status updates, which are reported to the room but acted on by nobody, because the room is not the person who can unblock the blocker. The person who can unblock the blocker is in a different team, in a different standup, answering the same three questions to a different room.
The Fifteen-Minute Lie
The standup is timeboxed to fifteen minutes. This is a lie agreed upon by everyone who has ever attended a standup.
The standup takes fifteen minutes when the team has three people and nothing to discuss. The standup takes forty-seven minutes when someone shares their screen, someone else asks a follow-up question, the follow-up triggers a design discussion, the design discussion reveals a dependency on another team, and the Scrum Master asks if anyone has “anything else” — which someone always does, because humans abhor the silence that signals a meeting’s end.
The standup’s duration is inversely proportional to the team’s need for it. Teams that communicate well have nothing to report. Teams that communicate poorly have everything to report and no ceremony short enough to contain it.
The Heartbeat Lesson
At a Scandinavian telecommunications company, a cross-team coordination meeting called The Heartbeat demonstrated what happens when a standup actually works.
The developers attended. They discovered who in other teams they needed to talk to. Then they reached out immediately — instead of waiting for next Tuesday. Within weeks, only the scrum masters attended the meeting. A manager panicked: “The Heartbeat is broken.”
A consultant walked the floor instead of sending an email. The developers told him: the meeting was incredibly valuable. So valuable that they had already extracted everything they needed and were solving problems in real time.
The standup had graduated. Its empty room was not failure — it was proof of success. The best standup is the one that teaches people who to talk to, so they stop needing the standup to talk.
See: Big Room Planning#The Heartbeat
The Lizard’s Standup
The Lizard does not stand up. The Lizard does not sit down. The Lizard is cold-blooded and horizontal, which is the optimal posture for shipping software.
The Lizard’s standup takes zero minutes because the Lizard’s team is one, the Lizard’s blocker is none, and the Lizard’s status is the commit log.
“The Lizard has never attended a standup, a retrospective, a sprint planning session, or a PI planning event. The Lizard has also never shipped late.”
— Agile
Why It Persists
The standup persists because it solves a real problem — the problem of people not knowing what other people are doing. In organizations where people sit in different rooms, work on different features, and communicate through JIRA tickets, the standup is the fifteen minutes a day when they are forced into proximity.
That the solution is to force people into proximity — rather than creating conditions where proximity happens naturally — is itself the diagnosis. The standup is a treatment for an organizational structure that prevents communication. It does not fix the structure. It patches it, daily, for fifteen minutes, standing up.
