Why Developers Hate Monday Standup
Why Developers Hate Monday Standup
Monday mornings are notorious for being the most dreaded day of the week, not just for regular people but for developers too. This is because of a mandatory meeting that takes place at the start of each week known as the Monday Standup. Although the Monday Standup has been implemented to improve communication and productivity in software development teams, many developers seem to despise it. In this article, we will discuss why developers hate Monday Standup and what can be done to make it more bearable.
What is a Monday Standup?
A Monday Standup is a meeting where developers gather to share updates about their progress, identify any roadblocks or issues they may be facing, and plan their tasks for the upcoming week. The meeting usually lasts around 15–30 minutes and is facilitated by a Scrum Master or team lead. Each developer takes a turn to speak and is expected to share what they worked on last week, what they plan to work on this week, and any challenges they may be facing.
Why Developers Hate Monday Standup
- It’s a Waste of Time
Many developers see the Monday Standup as a waste of time. They argue that it takes away valuable time from their workday, and the information shared during the meeting can easily be communicated through other channels, such as email or chat. They feel that the meeting is just a box-ticking exercise and doesn’t actually add any value to their work.
2. It’s Redundant
For some developers, the Monday Standup is redundant because they are already in constant communication with their team members. They feel that they don’t need to share the same information they shared the previous week or discuss issues that have already been resolved.
3. It’s Disruptive
Enjoying this article?
Get more like it in your inbox — practical engineering leadership, fintech, and AI. No spam, unsubscribe anytime.
The Monday Standup can be disruptive to a developer’s workflow, especially if they are in the middle of a task or in a state of flow. Being pulled out of their work to attend a meeting can be frustrating and can impact their productivity.
4. It’s Too Early
Monday mornings are tough for many people, and the last thing a developer wants to do is attend a meeting that requires them to be alert and articulate. Some developers find it difficult to share their thoughts and ideas in the early hours of the day, and this can lead to a lack of engagement during the meeting.
How to Make Monday Standup More Bearable
- Keep it Short and Sweet
To make Monday Standup more bearable, it’s essential to keep the meeting short and sweet. Limit the meeting to 15 minutes or less and ensure that everyone sticks to the agenda. This will help to prevent the meeting from dragging on and will make it easier for developers to stay engaged.
2. Make it Relevant
Ensure that the information shared during the Monday Standup is relevant and valuable. Avoid sharing information that can be communicated through other channels and focus on the most important updates. This will help to make the meeting more productive and will show developers that their time is being respected.
3. Be Respectful of People’s Time
Respect people’s time by scheduling the meeting at a time that works for everyone. If possible, avoid scheduling the meeting first thing in the morning, and consider scheduling it later in the day when developers have had time to settle into their work. Also, be sure to start the meeting on time and avoid unnecessary delays.
4. Encourage Engagement
Encourage engagement by creating a safe space for developers to share their thoughts and ideas. Avoid interrupting developers or dismissing their concerns, and be sure to actively listen to what they have to say. This will help to make the meeting more collaborative and will encourage developers to actively participate.
In Conclusion
While the Monday Standup is intended to improve communication and productivity, it can often be viewed as a burden by developers.
Get new posts in your inbox
Occasional, practical notes on engineering leadership, fintech, and building with AI. No spam, unsubscribe anytime.
Comments (9)
Leave a Comment
Akua Boateng
May 18, 2023
Small addition: the incentives inside the calibration room matter as much as the actual conversation with the engineer.
Chukwuma Nwankwo
May 3, 2023
Does the approach here still hold on a 3-engineer team? We're at the smaller end of that and some of these patterns feel like they need a dedicated SRE to run properly.
Ebere Nnamdi
April 26, 2023
Small pushback: this framing assumes the engineer is receptive to feedback in the first place. In a team that has just been through a re-org the sequencing has to change.
Musa Musa
April 19, 2023
Does the approach here still hold on a 4-engineer team? We're at the smaller end of that and some of these patterns feel like they need a dedicated platform team to run properly.
Christopher Young
April 19, 2023
One more thing worth naming: the same techniques work about half as well when the team is fully remote across three timezones. The written-first shift really is the unlock.
Amina Hassan
April 13, 2023
Refreshing to read this framed for our market rather than lifted from a Silicon Valley playbook. Specifically the operational piece — the licence guys audit for it, and that changes the design constraints in ways the US-centric literature never touches.
Ikechukwu Umeh
April 8, 2023
The framing on "why developers hate monday standup" alone is worth the read.
Aliyu Suleiman
April 5, 2023
Refreshing to read this framed for our market rather than lifted from a Silicon Valley playbook. Specifically the operational piece — the settlement partners have opinions, and that changes the design constraints in ways the US-centric literature never touches.
Ikechukwu Ogbonna
April 5, 2023
Question on the second half — how do you actually apply this when the engineer disagrees? Struggling with that specific case on my service right now.
