Is the Daily Scrum not for collocated teams?
The assertion that the Daily Scrum is not recommended for collocated teams is false. It is false for the following reasons:
- The Daily Scrum is a non-negotiable requirement for all teams that do Scrum
- Collocated Scrum teams follow the exact same Scrum rules that distributed teams follow
What is a collocated Scrum team?
The word collocate means to place together. Generally speaking, developers on a Scrum team are collocated if:
- Members sit close together in a shared, open-office space
- Line of sight exists between Scrum team members
- Conversations between team members are easily overheard
- Members of the team work the same overlapping hours
The opposite of a collocated Scrum team would be a distributed team where each member is in a different geographic location. On a globally distributed team, members may not even work overlapping hours due to time change differences.
What happens in the Daily Scrum?
The Daily Scrum brings all the developers on the team together so they can informally discuss the three Daily Scrum questions, namely:
- What did you accomplish yesterday?
- What do you plan to do today?
- Have you run into any blockers to development?
This questions about whether the Daily Scrum is recommended for collocated teams plays into the misconception that if developers work together closely in a small, open space, then a Daily Scrum is not necessary, since the lines of communication are always open between members of the Scrum team.
It’s not an illogical thought. However, in terms of Scrum, the assertion that there are situations where the Daily Scrum is not needed is false.
Scrum demands that the Daily Scrum occur every workday throughout the Sprint, regardless of whether the team members are collocated or not.
The Daily Scrum and collocated teams
Many people complain that there are too many meetings in Scrum. The Daily Scrum is typically the target when such complaints arise.
Scrum practitioners should remember that the Daily Scrum does not need to be an heavily formalized ritual. Yes, it’s timeboxed to 15 minutes, but that’s an upper limit. That doesn’t mean the Daily Scrum can’t be shorter.
If three are four developers are all collocated in the same room, they will naturally talk to each other when they arrive for work in the morning. Casual conversations are a natural thing that happens when people work together.
When you see a co-worker in the morning, you naturally talk about things like:
- Last night’s hockey game
- The traffic on the way in
- The things that you accomplished yesterday
- How much the last email you got from management annoys you
Scrum simply wants developers to harness the natural desire for people to converse with each other and focus it for maybe five or ten minutes and have developers working together talk about:
- What they’re excited about having accomplished recently
- What they’ve set their mind to accomplishing together
- Insights they’ve learned that they want to share with the team
- What issues they may need help with in order to achieve the Sprint goal
Collocated teams can’t skip the Daily Scrum
The Daily Scrum is just a chance for developers to catch up with each other, discuss their progress and adjust their plans if any unforeseen circumstances have arisen.
The Daily Scrum shouldn’t be over-formalized, it shouldn’t be run like a status meeting and it shouldn’t feel like a hindrance. If it does, you’re not doing the Daily Scrum right.
The Daily Scrum must run every single workday during a Sprint or else your team is engaging in ScrumBut. As the Scrum Guide says: “The Scrum framework is immutable. While implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety.”