Daily Stand-up Meeting Template

Overview

The daily stand-up is a short, focused synchronisation ceremony designed to keep teams aligned and surface blockers quickly. Lasting no more than 15 minutes, it brings every team member together at the same time each day to share progress, plans, and impediments.

Originally popularised by Scrum, the stand-up has become a staple across agile and non-agile teams alike. Its power lies in brevity and consistency. By enforcing a strict time limit and a predictable three-question format, the ceremony discourages long-winded status reports and encourages focused, actionable updates.

The name "stand-up" comes from the practice of physically standing during the meeting. Standing creates a natural incentive to keep things short, because nobody wants to stand around listening to a 30-minute monologue. Even for remote or distributed teams, the principle holds: keep it tight, keep it daily, keep it useful.

When to Use This Framework

The daily stand-up works best for teams that collaborate closely on shared deliverables and need frequent coordination. Consider using this format when:

• Your team is working on interdependent tasks where one person's progress affects another's ability to start or continue their work
• You need to detect and resolve blockers within hours rather than days
• Team members are distributed across multiple locations or time zones and lack informal opportunities to share updates
• You are running fixed-length iterations (sprints) and need to track daily progress towards a commitment, complementing your sprint planning with ongoing coordination
• You want to build a cadence of accountability without resorting to micromanagement
• Your team has recently formed and needs a reliable touchpoint to build cohesion and shared awareness

Who Should Attend

Sample Agenda

Example Use Case

Consider a cross-timezone engineering team of eight people spread across London, Berlin, and Bangalore. The team is building a payments integration and is midway through a two-week sprint. They hold their daily stand-up at 10:00 AM GMT, which is 11:00 AM CET and 3:30 PM IST.

During Tuesday's stand-up, the front-end developer in Berlin mentions she has finished the checkout form but cannot test it because the API endpoint from the back-end developer in Bangalore is not yet deployed to the staging environment. The facilitator in London captures this as a blocker and immediately after the stand-up connects both developers on a quick call. By lunchtime, the endpoint is deployed and testing begins the same day.

Without the stand-up, that blocker might have gone unnoticed until the Berlin developer raised it in a Slack message hours later, potentially losing an entire working day. Multiplied across a sprint, these small coordination gains compound into significantly better velocity and fewer surprises at the sprint review.

Best Practices

• Start on time, every time. Do not wait for latecomers. If people learn the meeting waits for them, punctuality will erode quickly.
• Keep it to 15 minutes or less. If the team cannot finish in 15 minutes, the group is either too large or people are going into too much detail.
• Talk to the team, not the manager. Updates should be peer-to-peer coordination, not upward reporting. The facilitator guides the process but is not the audience.
• Use a visible task board. Walking the board (reviewing cards from right to left) keeps discussion anchored to actual work items rather than vague summaries.
• Take detailed discussions offline. When a topic needs more than 30 seconds of back-and-forth, note it down and schedule a follow-up immediately after the stand-up.
• Rotate the facilitator role. Sharing facilitation builds ownership and prevents the ceremony from feeling like a status report to one person.
• Choose a consistent time that works for all time zones. For distributed teams, use a tool like Meeting Planner to find an overlap window. Prioritise a time that falls within business hours for the majority.
• Record blockers visibly. Use a shared document, Jira board, or Slack channel to log blockers so they are tracked to resolution and nothing falls through the cracks.

Common Mistakes

• Turning it into a status report. When team members direct their updates at a manager instead of each other, the meeting becomes a reporting ceremony rather than a coordination tool.
• Allowing problem-solving during the stand-up. Deep-diving into a technical issue consumes the entire time box and disengages everyone not involved. Solve problems afterwards.
• Skipping the stand-up when things are "going fine." Consistency is what makes the ceremony effective. Cancelling it erodes the habit and means blockers surface later than they should, often only emerging during the sprint retrospective.
• Including too many people. Stand-ups work best with 5-9 participants. Larger groups should split into sub-teams with their own ceremonies.
• Not following up on blockers. If blockers are raised but never resolved, the team loses trust in the process and stops mentioning them.
• Scheduling at a time that excludes part of the team. If your stand-up time forces some members to join at unreasonable hours, resentment builds and participation drops. Find a fair overlap.
• Running the meeting while seated with laptops open. For co-located teams, sitting down with screens encourages multitasking and longer discussions. Stand up, stay focused, and finish fast.

Related Templates

Related Tools