Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Scattered Meeting Day Syndrome

DZone's Guide to

Scattered Meeting Day Syndrome

Free Resource

“Automated Testing: The Glue That Holds DevOps Together” to learn about the key role automated testing plays in a DevOps workflow, brought to you in partnership with Sauce Labs.

image I have observed that the most unproductive day would be to have scattered meetings all throughout the day.  

For example:


  • 9- 9:30 AM   First meeting
  • 10 – 12  Second meeting
  • <Lunch break>
  • 2 – 2:30 Another meeting
  • 3 – 4  Last meeting of the day

After the first meeting, one would rush to get a coffee to prepare for the second one. By the time you grasp the second one, the bell rings for lunch. The day continues with meetings with a break of every half an hour, and end up with a pile of “real work” by 4 PM, causing too much stress. This leads to too many meetings syndrome

This is exactly what the Agilists dislike. In fact I have heard people saying that Scrum has too many meetings!   As per various research, the task switching could cost nearly 40 percent productivity loss.

Solution

Personally, I found that blocking a chunk of a day provides me the well deserved and dedicated focus.  Have others seen this happening?   Have you experienced this?  How do you deal with this scattered meeting syndrome?



Learn about the importance of automated testing as part of a healthy DevOps practice, brought to you in partnership with Sauce Labs.

Topics:

Published at DZone with permission of Venkatesh Krishnamurthy, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}