Daily Scrum: Keeping the team connected
Most teams have heard of the Daily Standup. Fifteen minutes, same time, same place, every day. In Scrum, it's called the Daily Scrum and it's one of the most consistently misunderstood events in the framework.
Done well, it's the heartbeat of the Sprint. Done poorly, it's the meeting everyone dreads and nobody learns anything from.
What is the Daily Scrum?
The Daily Scrum is a 15-minute event held every working day of the Sprint, at the same time and place. It's commonly called the Daily Standup and the two terms are often used interchangeably.
It's a Developers' meeting. That's worth saying clearly because it's one of the most frequently ignored rules in Scrum. The Daily Scrum is for the people doing the work. The Scrum Master and Product Owner can attend as observers. They're not there to run it, report into it, or be reported to.
Grounded in the Scrum Guide and the Agile Manifesto, this RAFT is CoLab's take on how to make it work in practice.
This is one of four events covered in our Back to Basics with Scrum Events, if you want to see how it fits the wider Sprint rhythm.
What We Focus On
The three questions most teams use - what did I do yesterday, what will I do today, is anything blocking me - are a reasonable starting point but they have a well-known problem: they focus on individuals, not the team.
The 2020 Scrum Guide removed the three questions entirely, leaving teams free to choose their own structure.
Here's what we focus on in our coaching.
Start with the Sprint Goal
Before anything else, remind the team why this Sprint exists. Read the Sprint Goal aloud if it helps. Then ask the question that actually matters: are we still on track to achieve it? If the answer is yes, great. If it's uncertain or no, that's a conversation to have right now, not at the Sprint Review.
Make the time work for everyone
Find a time that suits the whole team. Negotiate the earliest time that genuinely suits everyone. It's a Daily Scrum, not a morning Scrum.
Keep the Sprint backlog in a good state
Making work visible is a powerful tool we can use to create transparency. That means adding on to the Sprint backlog the urgent production problem the team is dealing with and the security upgrade to our containers and deployment tasks we have to manage with the DBA team. It makes it obvious what the team is dealing with and facilitates coordination within the team.
Nominate a facilitator
Most teams now work distributed at least some of the time, with the Daily Scrum on a video call. The Scrum Guide doesn't call for a facilitator, but someone still needs to share the board and keep the conversation moving. Cameras on helps. Taking a turn facilitating is worth encouraging early, the job is to serve the conversation, not lead it.
Keep it fresh
Mix up the conversation. Some days, going from person to person is fine, it gives everyone a voice. If the Sprint Backlog looks a bit messy, it is time to walk the board. Find the items that are not moving. Ask the hardest question - what help do you need? And don’t take no for an answer.
Flag it, don’t solve it
It is amazing how much conversation and coordination an established team can fit into 15 minutes. If something needs a longer conversation, the facilitator flags it and schedules time with the people who need to be involved. Not every problem can be solved during the Daily Scrum.
Why We Love It
A well-run Daily Scrum:
Creates a daily moment of connection. Before anything else, the team checks in with each other. Not just on tasks but on how people are actually doing. That human layer matters more than most teams realise.
Keeps the Sprint Goal visible and alive. It's easy for teams to get buried in tasks and lose sight of why the Sprint exists. The Daily Scrum is the daily reminder.
Surfaces problems early. A team member who's been stuck on the same item for two days is a signal. A task that hasn't moved in three days is a signal. The Daily Scrum is where those signals show up before they become Sprint-ending problems.
Replaces the need for most other check-ins. When the Daily Scrum is working well, managers and stakeholders don't need to chase updates. The transparency is built in.
Builds self-management. The team coordinates its own work. Nobody assigns tasks or directs traffic. That's where real ownership comes from.
When We Use It
Sprint Planning happens at the start of every Sprint. But the quality of it varies enormously from team to team. We pay extra attention to how a team plans when:
A new team is forming and needs to build the habit of planning and committing together.
The team keeps missing their Sprint Goal and nobody's quite sure why.
The Sprint Backlog is consistently overloaded and the team is always chasing its tail.
There's no real Sprint Goal - just a collection of items with no connecting thread.
Unfinished work is rolling over Sprint after Sprint without being questioned.
Things to Look Out For
It's become a reporting meeting - people are giving updates to the Scrum Master or a manager rather than talking to each other. The dynamic is wrong.
The Sprint Goal isn't mentioned - if the team goes through the whole event without referencing why the Sprint exists, it's just a task update. Even if you are doing Kanban, the team must be very clear what they are focused on at any point in time.
The same items keep appearing - if nothing’s moved in two or three days, something’s stuck or too big, and it needs attention.
It runs long - fifteen minutes is enough when the team is focused. Consistently going over usually means the meeting is doing too many jobs.
People are skipping it - that's feedback. Either the time doesn't work for everyone or the meeting isn't valuable enough to show up for.
Not meeting daily - some teams only meet two or three times a week and coordinate the rest over Teams or Slack. That's a red flag. We strongly encourage distributed teams to use these tools but they don't replace a daily conversation and reality check.
Managers or stakeholders are in the room - and it shows. It's hard to keep an open, transparent conversation when the people doing the work aren't the only ones talking. This is worth protecting, especially early in a team's life.
Try It With Your Team
If your Daily Scrum has started to feel like a chore, try shifting the opening. Instead of going straight to the three questions, read the Sprint Goal out loud and ask: are we still on track? See what that one change does to the energy in the room.
The Daily Scrum Troubleshooting Checklist gives the team a simple reference to keep the event focused and purposeful. Put it on the wall, pin it to your digital board, and use it until the habit sticks.
Track whether it's making a difference with the 3V Net Performance Score.
Our RAFT Series
✦ Our CoLab RAFTs - Rapid Agile Forecasting & Tracking skills - are practical tools we use every day in our coaching and training to help teams make work visible and performance-focused.
Curious? Let’s talk toni@agilecolab.com
Version 1, last updated on 6 August 2026
