Definition
A daily standup (also called the Daily Scrum) is a short, timeboxed meeting held every working day where team members synchronize their work and plan the next 24 hours. The classic format asks each person three questions: What did I accomplish yesterday? What will I work on today? What is blocking me?
The meeting is called a "standup" because participants traditionally stand to keep it short. In Scrum, the Daily Scrum is an inspect-and-adapt event specifically for the developers. The Scrum Master facilitates or coaches the team to self-facilitate, while the Product Owner may attend but does not direct the meeting.
The daily standup is distinct from a status meeting. Its purpose is peer-to-peer coordination. When one developer mentions they are starting work on the payment integration, another developer who built a related service last sprint can offer to pair or share context. This kind of spontaneous collaboration is the real value of the ceremony.
Why It Matters for Product Managers
The daily standup is your fastest feedback loop on sprint progress. In 15 minutes, you can assess whether the team is on track to meet the sprint goal without needing to check every ticket in Jira. You hear about blockers in real time instead of discovering them at the sprint review when it is too late to act.
Standups also surface requirement gaps early. When a developer says "I am not sure what the expected behavior is for edge case X," that is your cue to clarify before they guess wrong and build the wrong thing. PMs who skip standups often discover these issues days later during code review or QA.
For teams practicing Kanban instead of Scrum, the standup often takes the form of a "board walk," where the team reviews each work-in-progress item from right to left. This format naturally highlights bottlenecks and aging items. Consider using a cumulative flow diagram to track flow health between standups.
How to Apply It
- ☐ Schedule the standup at the same time and place every day (consistency matters more than the specific time)
- ☐ Enforce the 15-minute timebox strictly. Use a visible timer
- ☐ Focus on the sprint goal, not individual task completion
- ☐ Take detailed discussions offline ("let's talk after standup")
- ☐ Track blockers in a visible place and follow up on resolution within 24 hours
- ☐ Rotate the facilitator role weekly to build team ownership
- ☐ Try walking the board instead of the three questions if energy drops
For distributed teams, tools like Slack or Geekbot can run async standups on non-critical days. Reserve synchronous standups for 2-3 days per week when the team needs real-time coordination. The guides on sprint planning cover how standups fit into the broader sprint cadence.