posted 1 year ago
There are four events in Scrum, or as you'd call them, 'meetings.'
When someone says there are too many meetings, I always ask them which ones they'd remove:
You do a single planning session at the start of a month long Sprint.You do a review with the client at the end of a month long Sprint.You talk to your team about doing things better once at the end of a one month Sprint.
So no planning, not reviewing with clients and not team building ever? That sounds like a recipe for disaster.
Some get upset about the Daily Scrum, which is five or ten minutes where the developers just talk about how things are going and if any plans need to change in order to keep their short term goals in sight.
Imagine a team of 5 deveopers working an 8 hour day. In one day, they do a full weeks worth of work for one person, 40 hours. Don't you think after 40 hours of work the team should talk for 5 or 10 minutes? (Maximum 15)
Would you say a football team should cancel huddles between plays?
Hockey players shouldn't talk to each other before a faceoff?
Members of a team meeting and strategizing is a good thing. Doing it for a few minutes a day shouldn't be burdensome.
I'd certainly have a problem if we said we should eliminate the Daily Scrum and teammates should never talk to each other. Again, that's a recipe for disaster.
Scrum doesn't have too many meetings. Scrum gets it just about right.