hansHans Jonasson, PMP, CBAP, founder of JTC Unlimited, has over 25 years of experience in the areas of project management, business analysis and professional development training. Hans started his career with Volvo LTD in Gothenburg, Sweden, in 1980 as a systems analyst/programmer. In 1984 he moved to United States to work on new development projects for EDS and General Motors. He has managed all aspects of software development projects varying from $100,000 to $10 Million for the automotive industry. He has been a Project Management Professional (PMP®) and member of the Project Management Institute (PMI®) since 1996. He is a member of the Great Lakes Chapter of PMI® and the International Institute of Business Analysis (IIBATM), and a Certified Business Analysis Professional (CBAPTM). He has authored his first book titled Determining Project Requirements which was published in October 2007.

Project Control - Is it just an illusion?

In my last blog I was talking about earned value and my impression that it is not being used very much. I got some good responses to it and it seems like most of you agree. So, when going through the bloggers normal pain of finding the next topic to blog about, I got to thinking. What else in project management sounds good and right in theory, but is not always as pretty in real life? And project control jumped to my mind. One of those terms that sounds clear and scientific, but when you look behind the processes, it is not always pretty. I have been on many projects in my career, and I cannot say that I ever felt totally in control of one.

Now, I agree with the techniques that PMI uses to control projects. Variance analysis, corrective actions, earned value etc., are all ways to help us understand the project. But at the same time there is no doubt in my mind that the most important technique is informal communication with customers, team members, and other stakeholders. And yes, I know that PMI recognizes this communication as well, but since it is hard to clearly define and sometimes is more art than science, it tends to not get the attention it should.

Very few project managers will say in their lessons learned that the project failed because they did not spend enough time updating Microsoft Project, or calculating earned value, or even reviewing trend analysis. The most common cause of failure that I hear people talk about is a lack of communication; communication between organizations, between team members and especially between the project team and the customer.

For me the most important project control technique is the old "MBWA". Management By Walking Around. In other words, Informal communication, being visible, being accessible. The project manager who sits in the office looking at network diagrams will not have the same feel for the pulse of the project as the project manager who talks to the stakeholders on a regular basis. When you build a personal relationship with the team, the customer and others, you are much more likely to get honest feedback and early warnings. People may not want to tell you in a formal status report that there are some issues on the project, but one on one, once you have built trust they are much more likely to open up.

So project control has a lot of aspects to it, formal metrics are a part of it, but don't underestimate the value of just walking up to the customer, sitting down and asking; "How are things going?"

Don't forget to leave your comments below

Hits: 1905
Comments (5)Add Comment
...
written by markosantos, September 23, 2009
Informal chat works wonders, starting to talk about a football game, last nights TV show, a small joke, and then moving on to talking about the project. I use this technique to release stress, motivate and get better answers concerning work subjects.
...
written by jimwalker905, September 23, 2009
Would your views on metrics and trend analysis change if you saw some metrics and trends that supported your chats with people? I prefer trends that show me how team members are progressing weekly so that I can discuss sources of problems and possible solutions with the individual affected. This helps formal meetings deal with primary issues of delivery and lets informal chats catch those important bits of aditional communication.
...
written by lmote, September 23, 2009
Metrics & trend analysis let me know 'how it is going' before I ask the question. By doing some investigative work ahead of time, I can gently direct the conversation so that is productive and beneficial to all involved
...
written by kishan_solanki, September 24, 2009
Hans,

It is good to appreciate the value of informal communication. But one need to excercise caution, since poor handling of informal communication may lead to misunderstandings which are hard to explain. This may be an issue in environment of working with multi-nationalities. I believe that formal methods are very useful in such situations.

Regards

Kishan Solanki
...
written by markosantos, September 24, 2009
Here's a nice article on MBWA from NASA's Ask Magazine

http://askmagazine.nasa.gov/issues/35/35s_management_by_wandering.php

It points out exceptions and failures as well.

Write comment
We love to see comments! However, please do not market or sell any products. Your comment will be removed immediately!
smaller | bigger

busy