---
title: "What to Do When Teams Complain about Too Many Scrum Meetings"
url: https://daily.dev/posts/what-to-do-when-teams-complain-about-too-many-scrum-meetings-mpper1pzc
source_url: https://www.mountaingoatsoftware.com/blog/do-scrum-teams-meet-too-much
type: article
source: "The Mountain Goat Software"
published: 2025-01-28T17:08:45.464Z
updated: 2025-01-28T17:09:01.668Z
tags: ["productivity", "leadership", "agile", "project-management", "scrum"]
reading_time: 14
upvotes: 15
comments: 3
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# What to Do When Teams Complain about Too Many Scrum Meetings

**[The Mountain Goat Software](https://daily.dev/sources/mountaingoatsoftware)** · 14 min read · 15 upvotes · 3 comments

## Summary

Scrum meetings are often criticized for being time-consuming, but these complaints usually stem from misunderstandings or reluctance to adopt agile practices. Scrum requires minimal meetings, with only a daily fifteen-minute meeting plus a few longer sessions at the start and end of each sprint. Effective Scrum meetings occur at the right time, for the right length, and with appropriate focus. Scrum Masters should ensure meetings fulfill their purpose and manage time well. Resistance to meetings may indicate broader discomfort with agile principles. Emphasizing Scrum's benefits like visibility, customer feedback, and team coordination can help gain team buy-in.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.mountaingoatsoftware.com/blog/do-scrum-teams-meet-too-much>

## Community discussion

Top comments from developers on daily.dev.

**@przemelek** · 5 upvotes

> OK, I started to work before Scrum. My first company didn't have any process, first time I met process In Motorola in 2004, so long time ago when Agile was sexy new thing and we knew about one team doing it....  we had 1 weekly meeting, which took 1 hour. We didn't have daily, we had designs before coding, we had formal code reviews (with paper!) and we still spend less time on meetings that in some of "scrum teams" I worked later ;-)
> Later I remember having 2-3 hours planning each two weeks, each week 1-1.5 hour grooming (now backlog refinement) and 1.5 hour demo + daily each day taking...

**@adam47** · 2 upvotes

> Have a scrum meeting about it

## Similar posts on daily.dev

- [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments
- [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments
- [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments

---

Tags: [#productivity](https://daily.dev/tags/productivity), [#leadership](https://daily.dev/tags/leadership), [#agile](https://daily.dev/tags/agile), [#project-management](https://daily.dev/tags/project-management), [#scrum](https://daily.dev/tags/scrum)

[View this post on daily.dev](https://daily.dev/posts/what-to-do-when-teams-complain-about-too-many-scrum-meetings-mpper1pzc)
