2 ms·
Too many meetings is a sign of people not knowing what they are doing. So they need to get together ever so often to see where they are and what to do next. Th
by thisisit 9y ago
Too many meetings is a sign of people not knowing what they are doing. So they need to get together ever so often to see where they are and what to do next.
Then there is a case of everyone reading about agile and all it's ilk without understanding it completely. Everyone wants a "daily stand up" update meeting for every "project" out there. Then if there are issues, you need a separate "issue discussion meeting". Then there has to be "team meeting" to discuss what is going on in the team. The list goes on and on.
I also find that many a times, daily stand ups instead of being short, sweet 30 seconds update are just meandering stories trying to give color to a rather dull and boring day of work.
In my experience, surprisingly it wasn't a bank which had more meetings but a pure play IT product company. We were a team of consultants working on different projects so we had -
monthly team planning meeting,
daily status meeting,
design meeting,
executive action committee meeting,
weekly specific project status meeting,
daily status with the manager,
weekly status with manager's manager,
monthly status with manager's manager's manager (yes two times removed),
couple of "issue" meetings.
Average 1 hour meeting every day with at least 2 hours of prep required. So 3 hours everyday was gone just like that.
- maxxxxx 9y agoThis looks about right. And if the project falls behind then create a "drive team" that tries to figure out why no actual work is being done.