This is how it goes: The title of the anti-pattern is Death by Planning, the sub title is the meeting will continue until morale improves
This is the link to the calendar page http://deviq.com/death-by-
The elaboration for the anti-pattern is: The act of over-planning for software development projects, which by nature are very chaotic and often run into problems that cannot be plan for.
The further elaboration from the web site is read as the following:
Although planning is an essential part of building quality software, keep in mind that shipping is a feature<http://deviq.com/
Also, keep in mind the expense associated with meetings. If six people who make an average of $60,000 in salary meet for an hour, and their benefits, etc. costs another 30% above that, the meeting costs the company about $225 (assuming 40-hour work weeks, etc.). You can install a meeting cost app<https://www.google.com/
It's a good idea to minimize how much time is spent on meetings. You can't eliminate them entirely, and the larger your organization, the more time is required to keep everybody on the same page. However, you can keep meetings shorter by having specific agendas, using standing meetings where possible, and minimizing who needs to attend meetings. Just these three simple techniques can make a significant difference. Starting on time and ending on time are also a big help in limiting how much time is wasted by meetings.
Quote for the anti-pattern is "Everybody has a plan until they get punched in the face" -- Mike Tyson
In my 15 years working in the US IT industry, I have had 10 jobs. They are from in-house IT department to IT consulting firm; from small shop total headcount 10 people to large MNC. Throughout the time working with these companies, I observed one thing: that is the number of meetings, the less chance the project would be success. There are individuals I have seen are very special. For one they are very busy, for two they are all busy in attending meetings. As if their job is attending meetings, no deliverables before the meeting, no action items after meeting. From 9:00 to 5:00 they simply jump from one meeting to another.
I also have seen some individuals who try to avoid meetings, because they believe they are too busy to attend meetings. They have some more important deliverables to produce. Offer I see these 2 group of people do not work well together.
It is given, that meetings are necessary in any software development project. For all attendances, for them to be motivated to attend meetings, they need to feel be benefitted. Similar to documentations, for these who produces documentation, they need to believe the documentation will help them in their work.
The following are some possible benefits for attending meetings:
1. I have some ideas I want to explain to others so that they accept my ideas and work in the way I prefer them to work
2. Someone has some ideas to explain to me so that I can produce the result that works with everyone else
3. Something to taught or something to learn
4. There are some disagreement, we want to establish some common understanding through the meeting, so that the result we produce can work together well.
From the list you can see, meetings are not the starting points, neither end points. You either bring your value to the meeting or take away some value from the meeting to do your work or both. As all know, the most effective communication is face-to-face conversation. For meeting organizer, to make a group of people into one room have face to face conversation is the most effective way of communication, but it is also most expensive way of burning man-hours. Use it with the cost in mind. For meeting participants, bring your value to the meeting and make the meeting valuable to your work. For those who are meeting goers, I suggest you realize your value beyond meetings.
No comments:
Post a Comment