I have my own opinions on this subject, but would like to hear/see something from someone with a bit more clout. I am trying to convince our Task Leads and Sr. Management that "weekly" and "monthly" meetings DO NOT belong in a project schedule!!! Rather, a lengthy overarching activity called, "CIP Meeting Support", for example, should be used.
We currently have so many meetings in our "legacy" IMS that roughly half our our 1800 activity network represents them - yes, about 900 weekly or monthly meetings!
Does anyone have an opinion on this or can you point me to a quote or some other piece of information where this issue is discussed?
Many thanks... Saving Changes...
Sort By:
Anonymous
From my experience (12 yrs PM) it depends on what you are using your plan for. Is it for schedule or schedule and time tracking? If it is for schedule than your tasks should coorelate to a deliverable - a meeting isn't a deliverable and rarely do you produce a deliverable out of a meeting. However, if there is a need to track at a very detailed level all time towards a project and the plan is the only way to do this, then you would need to account for these meetings. However, I would in this case put a large bucket that is labeled meetings that time could be tracked against. There would be no need to try and have a different task for every type of meeting. In the end you have to ask yourself does the benefit of doing this type of tracking outweigh the cost (time) to do it? Saving Changes...
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Dear Dan, like you advocate, we do not include the meetings for "CIP Meeting Support" in the project schedule. In our environment, to do so would not only inflate WBS items, but it could potentially mis-represent project time and cost to a specific customer project. I hope to read other posts on this. Thanks. -- Mark Perry, VP of Customer Care, BOT International Saving Changes...
