Vote with your Feet

What value do you get from your Scrum meetings? This was the question posed to a team when I heard the usual “Scrum has too many meetings” complaint. I asked each member to write a % number for each meeting they attended. It ended up like this.


In summary:


If I went to meetings, that on average gave me only 50% value I’d likely share the mindset that there are “too many meetings in Scrum”.

I actually don’t believe that. I believe that Scrum has exactly the right amount of meetings. We meet in order to align i) with our customers, and ii) with each other. Without alignment we get lost, we work on things of dubious value, and we have no idea who cares about what we do. As a developer I’d rather write code than spend time in meaningless meetings.

A common solution to this problem is to stop doing Scrum, or reduce the number of meetings. In the case above planning would be the first to go—with only 43% it is the biggest time drain. But if we don’t plan—which means to make decisions on what to do next in order to achieve our purpose—then what do we work on? Vagueness and disgruntlement will will be our companions for the next week or two, or until that urgent extra meeting where we are called together to be told we’re working on the wrong thing, or working too slowly—or both (!)

So often I’ve heard words to the effect of “Scrum doesn’t work for us so we are going to do Kanban”. Kanban is seen as the soft option, allowing teams to meet less, talk less, and worst of all shy away from the dysfunction that Scrum has began to unearth. Kanban isn’t intended to be a cop out, but sadly that is how it’s so often perceived by those who struggle with Scrum.

The problem is not too many meetings, it is too many ineffective meetings. This comes back once again to organizations seeing Scrum as a process, and missing the principles. Telling people to meet every day, when in fact they are all working on different tasks for different features and have nothing to share with each other is surely a waste of time, likewise meeting with a PO who hasn’t given forethought to his requests, or attempting a retrospective when no one is willing to actually take action to change anything.

Rather than abandoning alignment, get better at it. Make your meetings useful. Or at least attempt to. Begin meetings with a clear, prioritized agenda. Start and finish on time. Avoid rabbit holes. If you are bored, disconnected or confused, say so. Ask for clarity, get involved, challenge, confront, ask questions. If you are at a meeting where you are not adding value and not getting value (the two usually go hand in hand) then vote with your feet. Leave the room. Do something meaningful instead. But don’t disengage. Prepare for the next meeting to go differently.

Every meeting you attend should have 100% value for 100% of the participants. If you fall short of this, reflect and improve.

Scrum meetings, when effective, engage and motivate people, establish focus, allow everyone to be aligned on the journey, and reduce unnecessary waste. The meetings are not overhead, but sometimes the attitudes are.

[comments removed]


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s