Daily Scrum

The daily scrum, often called the daily standup, is a short event in the Scrum framework where the team meets — usually for fifteen minutes, at the same time and place each day — to synchronize their work and plan the coming day toward the sprint goal. It is one of the framework's defined events, and it belongs to the people doing the work: the developers, not managers or stakeholders. The classic form has each person touch on what moved the team toward the goal, what they will do next, and what is in the way, though modern Scrum treats the exact format as the team's choice as long as the meeting inspects progress and adapts the plan. The name and the standup habit both push toward keeping it brief.

The purpose is coordination, not status reporting. The daily scrum exists so a team working toward a shared goal can adjust together every day — spotting where efforts overlap or diverge, surfacing blockers while there is still time to act on them, and re-planning the day around what is actually true rather than what the sprint plan assumed. Because software work changes fast, a daily rhythm of inspect-and-adapt keeps the team pointed at the sprint goal instead of drifting for a week and discovering problems too late. Done well, it replaces a scatter of one-off check-ins and interruptions with a single predictable moment of alignment, and it makes blockers a shared problem the team resolves rather than a private struggle.

The daily scrum is often mistaken for a status meeting, and the difference is the whole point. A status meeting is for reporting upward — each person tells a manager what they have done, and the manager collects and judges it. The daily scrum is for the team to coordinate with itself. It is held by and for the developers, not to inform a boss but to plan their own day. When a daily scrum degrades into everyone reciting yesterday's tasks to a manager, it has quietly become a status meeting, and it loses its value: people perform for the manager instead of solving problems with each other, and the meeting stops changing what the team does that day.

The tells are easy to spot once you know them. In a status meeting, people talk to the person in charge; in a daily scrum, they talk to each other. A status meeting produces a report; a daily scrum produces an updated plan and a list of blockers to clear. A status meeting can run long because its job is thorough reporting; a daily scrum is deliberately time-boxed because its job is quick alignment, with detailed problem-solving taken offline afterward. Keeping the daily scrum a team event, not a management ritual, is the single most important thing about it. The moment its audience becomes a manager rather than the team, its purpose has changed, whatever the calendar invite still calls it.

Run the daily scrum by holding it at the same time each day, keeping it inside its time box, and aiming it at planning the day rather than reporting the past. Let the developers own it, focus on the sprint goal and on blockers that need clearing, and take deep problem-solving offline into a follow-up with just the people involved, so the whole team is not held hostage to one issue. Make blockers concrete and assign someone to resolve each, so the meeting ends with actions rather than just information. If people are talking to a manager instead of to each other, correct it, because that drift is what turns a daily scrum into the status meeting it was meant to replace.

The failures are letting it run long by solving problems in the room, turning it into a status report to a manager, treating it as a rigid three-question script rather than a planning session, and ending with noted blockers that no one owns or clears. Skipping it when things get busy is another trap, precisely when alignment matters most. The discipline is a short, team-owned, goal-focused daily sync that surfaces and assigns blockers, adapts the day's plan, and pushes detail offline — so it stays a fast coordination event for the people doing the work, not a meeting performed for someone in charge.

The daily scrum is a defined event of Scrum, the agile framework introduced in the 1990s and codified in the Scrum Guide by Ken Schwaber and Jeff Sutherland.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where daily scrum is a core concern: