How to have a successful project meeting

If you are a senior project manager, program manager or team lead, you may view meetings as a high-probability time waster. And, moving into the management of projects seems to have given you a whole new set of “go-to-meeting tickets”—many of which do not directly affect accomplishing your project objectives. As a project manager, you should be aware of the danger of becoming part of the problem instead of part of the solution. So, is it possible to have successful project meetings?

Yes. (Thank heaven!)

It is actually not that hard.  First, think about your real goals for project meetings:

  • Gather status information
  • Identify any problems that may impact the schedule or budget
  • Resolve conflicts and facilitate teamwork
  • Brainstorm or walk through problem-solution spaces (to create a common understanding and take advantage of the collective knowledge of your team)
  • Flow information to the teams, team members and project staff

Now, reflect on what you hated about some meetings you were required to attend. Try to be specific in your ruminations—don’t say “it wasted my time”—think seriously about what behaviors made the meeting seem useless or worse. If you hear yourself thinking:

  • “We sat around for 30 minutes waiting for people to get there”
  • “No one knew what the meeting was about”
  • “We spent an hour doing something that could have been accomplished in 10 minutes”
  • “We re-hashed the same old things”
  • “No one listened; they just wanted to hear themselves talk”

Well, your internal list should give you some pretty good ideas of what not to do or what to avoid.  So, what are some positive ideas for making your project meetings successful?  Try this list as a start.

10 ways to make your project meetings successful

  • Have an agenda, share it before the meeting, and follow it. If an attendee is supposed to have data, answers, or provide input; let them know beforehand so they will be prepared. Also give others an opportunity to add items to the agenda that they feel need to be discussed by the team.
  • Start on time and end on time—or even early (if all items have been addressed). Mornings often work better than afternoons and Tuesday is a good day.
  • If you will be reviewing status and task prioritization at a project meeting, be sure that all critical participants are going to be there. This is especially important if the meeting will involve decisions affecting the project tasking for the upcoming week. If everyone hears the same message, the chance of conflicts later on will be minimized.
  • Take notes on results that track to the agenda and capture all action items. Share this as an email within 24 hours. (Or utilize a good collaborative tool like SharePoint)
  • Food or no food? Opinions are mixed on this, but I tend to come down on the side of not providing treats. It is just one more thing to do and folks can bring a snack or drink if they want it. Save the treats for celebrations or in recognition of extraordinary efforts or stresses.
  • Dealing with conflict. Not all conflict is bad or unavoidable. Your job is to keep the talk relevant, not personal; focus on outcomes not playing the blame game.  Remember, healthy tension is all right.
  • Every meeting must have a leader. It does not always have to be you, but someone must be in charge and facilitate the meeting.
  • Try to make sure that everyone who has something to say is given a chance to say it. You do not need to take turns, but be alert to body language and participation. If someone seems overly quiet, ask them a question.  Remember that silence is not always golden—everyone likes to contribute.
  • Decide beforehand if you will allow cell phones or texting during the meeting—I personally hate personal devices in a meeting and ask people to NOT use them. If the meeting is long, give a break for people to catch up with messages.
  • Ideally your meeting should be no longer than two hours and shorter is better. Meetings that run on tend to dull the spirit and the mind.  I prefer the 50 minute meeting – just short of an hour but long enough to get the job done!

Here are the thoughts of some other meeting pros:

“Meetings suck, but they don’t have to”

“6 Key Tips for Running Effective Project Meetings” by Duncan Brodie

Running a Productive Project Meeting  from The Manager.Org

 

Do you have any good tips for meetings?  Write a comment and share!

 

Successful strategic planning requires project managers

When you read papers, magazines or listen to the news today, do you wonder what happened to Business Strategy or Strategic Planning?  Strategic plans deal with reaching your organization’s future goals within a two to five year time frame. It should be the touchstone in making decisions about the allocation of resources necessary to achieve an organization’s vision. The importance of a strategic planning roadmap is well stated in this dialogue between Alice and the Cheshire Cat (Alice in Wonderland by Lewis Carroll, Chapter 6).

"Would you tell me, please, which way I ought to go from here?"
"That depends a good deal on where you want to get to," said the Cat.
"I don’t much care where–" said Alice.
"Then it doesn’t matter which way you go," said the Cat.
"–so long as I get SOMEWHERE," Alice added as an explanation.
"Oh, you’re sure to do that," said the Cat, "if you only walk long enough."

So, if strategic plans are so important to business success, why is it that completed plans so often only sacrifice trees and collect dust?  I believe this disconnect between strategic planning and day-to-day execution (called Project Management) is the direct result of how the strategic plan is built. When project managers are not part of the strategic planning process, there tends to be a lack of grounding in what can be done and how it should be accomplished.

If you are interested in my thoughts on this subject, I have recently written an article on The New Face of Strategic Planning—Bridging it with Project Management is the Key to Success.  Two web sites have been kind enough to publish my article.

http://www.projectsmart.co.uk/the-new-face-of-strategic-planning.html

http://www.pmforum.org/library/tips/2009/PDFs/apr/McGraw-New-Face-of-Strategic-Planning.pdf

 

And the original article is avialble at the Cognitive Library.

As always, I would welcome your thoughts and comments on this post.

 

My favorite project management links and websites

I want to thank those of you who have started reading the Blog and hopefully have found something useful in the posts.  But I am by no means the only “gray haired PM” in cyberspace.  I am grateful to the many project management veterans who have taken the time to share their experience and insight with the PM community. Along with the professional PM sites such as the Project Management Institute, which offers the Guide to the Project Management Body of Knowledge (PMBOK® Guide) – 4th Edition (available from Amazon hopefully soon), there is a wealth of PM information available on-line to help both the fledgling project manager and the seasoned professional. So in response to several of your emails, here are some of my favorite sites and blogs:

Project Connections provides for free access to papers, case studies, and almost 50 PM templates. They also have premium subscription services. You will find articles on lessons learned and best practices from people who are or have been project managers and lived to tell about it.

Projects at Work is an online magazine for project management professionals. It includes news, advice, and commentaries relevant to all aspects of project management.

Project Smart has an easy to navigate, topic references site with 100’s of articles and white papers on: Agile Project Management, Best Practices, Case Studies, Change Management, Communication and much, much more. This site serves as a useful and comprehensive knowledge base on all things related to project management.

PM Forum is all about international project management. From the PM forum, you can also access PM World Today. Each issue contains viewpoints by project managers, featured papers, case studies, and Tips and Techniques. PM World Today is a free subscription.

Project Perfect provides insight, worldwide commentary, and a products/services forum for project managers.

PM Today is a subscription service with informative articles on all aspects of project management. Although a subscription fee is associated with access, you can get 3 months free to check it out for yourself.

Cognitive Technologies Library is my own company’s resource library with lots of free white papers and guides for your reading and use.

Raven’s Brain is a great blog maintained by Raven Young where she posts on Project & Program Management, Leadership, Tech & Business, Personal Growth, Professional Development, Soft Skills and anything else that sparks her interest.

Journyx’s Project Management Blog is a great place to find posts from many authors on a wide variety of project topics.  And if you get to read one of Curt’s posts – it will always make you smile!
And lest we not overlook the need for your weekly dose of PM humor, don’t forget to check out Scott Adam’s Dilbert Strips.

While there are many more really helpful PM sites, I hope these examples will get you started.

If you have some favorite PM sites, please add them to the list via your comments.

 

Why identifying software project schedule risks is essential

Developing the schedule for a software project, especially one that is complex, may seem like a task equivalent to predicting when the stock market has reached bottom. That’s one of the best reasons I know for using predictive scheduling with frequent status monitoring and dependencies built in. But, I digress. Let’s say you are relatively new to the PM biz and you have been tasked with developing a software project schedule from scratch. How do you protect yourself, your team, and your organization from the risks inherent in this speculative venture?

In the best of all worlds, you will have an organizational history of developing similar software or solutions, a performance track record for the team members, and lessons learned from other projects. If any of this information is available, it gives you a solid foundation to begin identifying your project schedule risks and defending your estimates. Frequently, however, there is no good historical information to give you a leg up.  Your predecessor did not keep records or the organization didn’t value saving the history.  So you look at number of modules, estimated function points or how many lines of code need to be written, tested, and integrated. Then, you consider what potential risks must you account for in the schedule?  This is a key item for the project manager, because these are the things that will derail the project or cause all of the estimates to be woefully wrong.

What are some real world events that create schedule risks?
This list is not comprehensive and all of these will not happen on all projects. However, some of these events are likely to happen at some time during your project execution.  Therefore you should accommodate them in your risk management plan. (You do have a risk management plan, right?)

  • Coming up to speed on the customer’s problem so the solution fits their operating environment and expectations (Sometimes known as startup time risk)
  • Time required to learn and develop proficiency in new software tools, languages, hardware, or testing techniques (Also known as learning curve risk)
  • Delays in receiving hardware or software—“The memory board must be lost in the mail”; “Our shipping clerk is on maternity leave.”; “We can’t find your order.”; “Our computer system is down.” (Also known as the Murphy law)
  • Loss of a key team member
  • Finding and training new team member
  • Your partners are late delivering their pieces of the project
  • Disruptive team member
  • Shaking the bird cage—corporate reorganization, moving offices, acquiring a new company or being acquired (Also known as the Annual Corporate event)
  • Interruptions from other critical, but not project related, tasks (One example is the holiday and vacation time in December)

Here is a bit of wisdom about scheduling and risk from the Herding Cats blog (“The Five Easy Pieces”)

  1. Hope is not a strategy
  2. All point estimates are wrong 
  3. Without integrating Cost, Schedule and Technical Performance you’re driving in the rear view mirror
  4. Without a model for risk management, you’re driving in the dark with the headlights turn off
  5. Risk Communication is everything

So, if you are now sufficiently worried, how should you identify and manage software development schedule risks?

Brainstorm. As a new project manager, you may not be comfortable trying to identify all the schedule risks on your project. So, pull your key team members together for a brainstorming session. Create what-if scenarios. Talk about what can go wrong. Develop a plan to deal with these risks.

Seek out training. Make sure all members of your team are up to speed on the software tools and operating environment. Work with HR or senior management to offer classes or consultation to improve developer’s skills before you have to rely on them to produce within schedule constraints.

Do your homework. The Project Management Institute offers A Guide to Project Management Body of Knowledge (PMBOK for short) for about $50 (less for members) covering all aspects of program management including risk management strategies. Or, you can get an extension of PMBOK from the Department of Defense  as a PDF download. You want to check out Chapter 11.   There are also good blog posts full of tips on the web like Randy McGowan’s post at ProjectSmart.

Keep communication lines open. Not wanting to hear bad news is a trait we all share. But, as the project manager, you need to know the risks your project faces and you want to know when someone on your team is concerned about achieving the planned schedule. Also, your senior managers do not like surprises. Keep them informed of your potential risks and always have a plan to deal with it, because they will ask.

I feel strongly that it doesn’t take fancy tools and teams of people to manage risks—it just requires some forethought and planning to address risk as a part of any project schedule.  Some of you might smile and call this “common sense.”

What do you think?  Leave a comment with ideas you have on managing schedule risk.

 

Follow

Get every new post delivered to your Inbox.

Join 354 other followers