Criticism of Scrum often revolves around perceived meeting overload, but such complaints usually highlight deeper issues. The problems usually arise from teams not understanding the purpose of Scrum meetings or lacking buy-in for agile practices due to poor past experiences. The article notes that Scrum's structure requires minimal meetings—such as a daily 15-minute check-in—and emphasizes that effective meeting management is crucial. It suggests that meeting fatigue can be alleviated by aligning team understanding of Scrum's objectives, which is a focus of educational courses offered by Mountain Goat trainers.
However, when a team complains about Scrum meetings, it's usually not truly a case of too many meetings in Scrum. Instead, these complaints are typically symptoms of one of two potential root causes.
Meeting fatigue is a common complaint from teams that are either new to Scrum or have drifted away from the purpose of each of these meetings.
I empathize with people who complain about meeting overhead. I hate meetings, too. Actually, I hate unnecessary or overly long meetings.
Getting the most out of meetings is something I and the other Mountain Goat trainers cover in our Working on a Scrum Team course, which is aimed at teams that are new to Scrum, or new to working together.
Collection
[
|
...
]