re: 9 Rules of Effective Development Team Meetings VIEW POST

FULL DISCUSSION
 
  1. Early in the morning, right after the stand-up.

I made a totally different experience on this one. After watching our "meeting culture" a while, it turned out that most people tend to be most productive in the morning, when the brains are still fresh.

When the day starts with a stand-up and (as suggested) even other meetings after this, the precious time in the morning is wasted in reporting and discussions with others.

When the "real work" (sorry, but this is most of the time what we're thinking, aren't we?πŸ˜‰) starts, peoples energy and motivation is already at a lower level.

Maybe they already feel, like they "lost" a discussion with a manager on how to do something, and are now upset. Or their "super elegant mega technical solution" was not appreciated as much as anticipated. And let's face it: Lunch break is only 0.5h / 1h / 1.5h ahead, so it doesn't pay out to start something big now, does it? 😎

Because of this insight, we moved the daily scrum an hour before the end of work (still time boxed at 15 minutes). Everyone tells what he did today, what he plans for tomorrow, just as suggested. Afterwards, there are 45 minutes left for meetings, so people have to express themselves short because they want to finish work soon.

Of course, sometimes the timespan won't be enough and there might be a meeting an hour before standup or something, but in general this works out pretty well, because the productive time from morning until shortly before finishing work is available to be...well, productive.

I also made the experience, that Meeting Days are beneficial once in a while like Martin wrote.

 

Why do you need meetings that "are not productive?"

 

I think I expressed myself wrong: Of course meetings should always be productive or canceled.

What I wanted to point out is, that in my experience it is more productive to program with a "fresh" mind and have meetings later :-)

It depends on the meeting. What if you need to make some decisions before you can program even? So they are blockers?

In general, though, I agree, that if programming activity is more productive than meeting activity, then it should go first. Still, meeting at the end of the day is basically useless (if it involves any decision-making), so having it somewhere at 2-3 as a middle ground might be a better idea.

Well in our case if we have to make decisions, we make it the day before 😊

It's really the same thing, just a different time...

I'm just coming out of our daily and a short "close-up" afterwards, because we had to discuss a little something for the work of my colleague for tomorrow. Now he knows what to do, has a bit time left to prepare his task and can start right in the morning having all the information he needs.

Of course this is a bit of personal taste - but as I wrote, it's just my experience that this works better for us.

This makes sense. It seems like you have the energy at the end of the day to make these decisions. And probably these don’t take much time (we’re not talking about 2-3h meeting in the evening that forces everyone to overtime (w/o being paid for it), right?).

code of conduct - report abuse