Our Daily Stand-up Is 15 Minutes. It Has Never Once Been 15 Minutes.
Ten in the morning. The daily stand-up starts on time, which turns out to be the last thing about it that goes to plan. We're eight developers on a scrum team, all remote. The meeting is boxed at fifteen minutes, and everyone knows it — it's right there in the calendar invite. Yet most days, around the point where the clock says fifteen, we're maybe halfway down the list of people, someone has…
At ten o'clock sharp, our daily stand-up begins. For a group of eight remote developers, the meeting is strictly timed at fifteen minutes, as clearly outlined in the calendar invitation. However, more often than not, around the fifteen-minute mark, someone inevitably starts to deviate from the planned agenda. Despite this seeming failure, the meeting tends to stretch well beyond its scheduled duration, and I've observed this pattern for long enough to view it more like a natural occurrence rather than a fault.
The meeting's structure follows a simple format - each developer shares their progress from the previous day, their plans for the day ahead, and any obstacles they're facing. This is a common practice across many teams, with the vocabulary largely in English, but occasionally translated into Japanese. The facilitator changes daily, rotating among team members, but this flat structure also eliminates a central authority to enforce a strict time limit.
This lack of a designated leader is both a feature and a challenge. While it encourages open discussion and avoids the hierarchical control often seen in meetings, it also leaves no one to cut off lengthy explanations or opinions. This leads to two main reasons for the meeting exceeding its fifteen-minute limit. First, the absence of a clear authority to regulate the conversation time allows discussion to flow freely, leading to extended conversations.
Second, much of the discussion often revolves around cross-team coordination or unresolved issues, which aren't strictly part of each individual's 'todays'. These external matters are often dealt with within the stand-up to prevent separate, longer meetings later. Consequently, even though the Scrum Guide prescribes a fifteen-minute duration, our stand-up often runs for around thirty minutes.
Despite the meeting's name, it's carrying more responsibilities than intended. It serves as a platform for resolving cross-team issues and facilitating open discussions, which are invaluable aspects of our collaborative work process.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
