Archive for May, 2009

Joys of Travel…or not?

I am on the other side of the world this week  -  at least the other side from my usual world. I am 8 hours out of my time zone, and it wreaks havoc on my business day. The simplest form of communication is now difficult. Juggling the time change so that I can call back home for anything to do with business or family becomes such a hassle.

3 oz. bottles, 1 bag, 1 traveler

3 oz. bottles, 1 bag, 1 traveler

The flights were a mere 15 hours total…oh yeah, and then 20 hours of layovers really added to the pleasure of the trip.

We take for granted too many of our local standards without realizing how important they are to our well being. Being able to call home or the office, to get some work done on the road and to relax are important processes that all executives and those in sales, service or business generally need to have available.

So far, my work day consisted of a 4 mile, one hour commute followed by 10-12 hours at the office, mostly waiting for others to actually get to the meetings. This will be followed by another 1-2 hours of traffic jams trying to get back to a little hotel room, get a quick meal, maybe do some work if the Internet is working and then crash-out. The joy of travel…not!

From David Egan

Photo from the TSA

Why Isn’t Formal Project Management More Widespread?

Editor’s note: this post is part of a series on formal project management techniques. For previous posts, click here.

In my last four submissions I defined formal project management and then argued that it decreases risks while saving money and time. If all these great things are true about formal project management, why isn’t everyone practicing it all the time?

There are three reasons why formal project management is not as widespread as it could be.

1. Ignorance – Not everyone is aware that there are better ways to introduce innovation into an organization than the natural or informal project management methods that develop spontaneously.

2. Apathy – People are resistant to change and do not want to fix systems that they perceive to be working “well enough.”

3. Lack of Effort – Formal project management requires discipline in terms of the team and the supporting organization.

Ignorance

Formal project management practices are relatively new to industries outside of construction and manufacturing. A lot of people and organizations are unaware of advances in project management practices such as those documented in the PMBOK (Project Management Body of Knowledge).

There is also a lack of consensus as to what constitutes the best practices. There are numerous organizations worldwide that advocate for their own project management practice standards. A lack of consensus makes it more difficult for newcomers to know what their organization should be doing.

Apathy

Many organizations already have successful project management programs in operation. These organizations – and particularly the project managers operating within them – do not feel the need for, and do not want, more structure and rules. They resist change because the changes do not necessarily serve the interests of the project managers.

Lack of Effort

Those organizations that recognize the benefits of formal project management practices must walk the talk if they are to be successful. Formal project management practices are like formal accounting practices. It will only work if the people involved (both directly and indirectly) make it work. Cooperation and support for formal project management practices start at the CEO level.

Moving from informal project management practices to formal requires effort and discipline. Not every organization is up to it.

Conclusion

Why isn’t formal PM more widespread? Because it is still a relatively new area of management science, which must prove its value to senior management before the discipline necessary for success will be encouraged throughout the organization.

But, it is coming! The benefits are too clear for formal project management practices not to spread far and wide over the coming years.

From Brian Egan

Image from webstockpro.com

Project Management and Procrastination

Procrastination… my old friend.

Every project I work on has milestones that seem to arrive at quicker pace than I can keep up. All of this is mostly due to procrastination – and maybe a little to do with perfectionism – but mostly just good old laziness. Almost anything is more fun than going back to try to finish that project lurking in the background of my mind, irking me as I move on to other, more interesting activities…like getting a drink or something to eat, walking my pencil around my desk…

Everyone experiences these days of wallowing in the sun and basking in past glories. They are just ways to recharge, refocus and get going again. Eventually, the hectic pace will return, and the lack of focus will pass. My usual method of dealing with procrastination (write a list out and start checking items off as soon as possible by taking the easy ones first and building up momentum for the final, dreaded activities) seems to usually work for me!

How do you handle your procrastination? I welcome your tips!

From David Egan

Image from Jessica Hagy of Indexed

Do Formal Project Management Practices Shorten Completion Time?

Editor’s note: this post is part of a series on formal project management techniques. For previous posts, click here.

Do formal project management practices help projects to finish earlier than informal practices do? Yes and no. Yes, because they ensure that time is well-utilized. No, because they force projects to meet stakeholders needs, not just be finished on time while delivering garbage.

Formal project plans almost always start-out with longer, initial duration estimates than would be the case for informal plans. This is because formal project plans are more likely to include all activities and to estimate with greater precision.

As a result of having longer duration estimates from the outset, formal project management practices are often blamed for “slowing projects down.” The time consumed by detailed planning and stakeholder approval is highlighted as just one of the more obvious delays. Slower decision-making and more complex change management processes are also assumed to cause longer project durations.

The fact is that even if formal project management requires more time up front, it almost always saves time in the long run, because what you plan for is more likely to be what you need. Informal practices may allow projects to get started earlier, but do not save time in the long run.

Informal project management allows work to begin before a formal, detailed and approved plan is in place. Work begins before there is a clear definition of everything that has to be accomplished. The gun is fired before it is properly aimed, so to speak.

Does getting started earlier save time? It may save time in special circumstances but certainly does not in most cases, because the wrong work gets done.

Formal project management practices save time by ensuring that the gun is properly aimed before it is fired. It focuses efforts on satisfying stakeholder needs rather than “getting started.” Formal project management saves time by avoiding wasted effort.

Formal project management accomplishes more, from the stakeholder’s perspective, in a given period of time than informal project management does. Informally managed projects that appear to take less time do so by accomplishing less from the stakeholder’s perspectives. Such projects may finish earlier, but do not deliver exactly what the stakeholders need or want.

From Brian Egan

Image source


The Downside of “Polite” Communication

Communication with family and coworkers can be frustrating. I find it particularly frustrating when I try to communicate with simple questions and get polite but not specific answers.  Now, I know people try to be polite when it comes to communication, and I am even guilty of it myself, occasionally. Let me give you an example. It’s 4:40 PM, and I ask my sister: “Are you hungry?” That sounds simple enough doesn’t it? However my sister will reply: “I had something to eat about 1:30 PM.” Now I have to decide if 3 hours and 10 minutes is long enough for her to be hungry again. Here’s where the game begins:

o    I could try to ascertain, for a person her height and body weight, how many calories she would burn per hour.

o    I could ask what she had for her last meal.  By finding out what she ate for her last meal, I could decide if it was a sufficient amount of food to sustain her for 3 hours and 10 minutes or longer.

o    I could ask her what activities she had been doing for the last 3 hours and 10 minutes to see if that would increase the calorie burn rate, causing her to be hungry.

There are many factors to consider. I think I’m going to have a nervous breakdown trying to collect all the possible inputs to determine if my sister is hungry!  Or, I could ask her to answer the question and be specific in her response.

I understand why people are reluctant to give a straight answer to a simple question. Many people want to be polite, and they feel that if they answer a question ambiguously it will allow the questioner to interpret an answer that will be agreeable to their position, and therefore, reduce the possibility of conflict. I contend that being ambiguous only causes frustration for the questioner, and makes the respondent appear to be unsure of them self.

I use the following exercise in my classes when teaching communication. I draw a line on the white board, divide it into 4 sections and label the line: 0%; 25%; 50%; 75%; 100%. I then write below that line the following terms:

1)    Just about
2)    Almost
3)    Close
4)    Looking good
5)    Not much more
6)    A tiny bit more
7)    Got started
8)    We have a bunch more to do

I ask each student to rate each one of the terms on a scale of 0% to 100% on how close to “finished” each of these terms mean. This is always good for a couple of laughs, but the point should be taken that ambiguous communication is not helpful when reporting the progress of activities in a project.

It is your responsibility, regardless of your position, to be specific when reporting on progress. If you are the project manager it is your responsibility to make sure you understand exactly what individual contributors are reporting. You can typically get away with being polite at the expense of being specific in a social situation. Although it may frustrate the questioner, there is no harm done. In a business setting you can still be polite, but you must also balance that politeness with being specific. Without specific communication, project managers risk losing control of their projects.

More on the dangers of allowing incongruent communication later…

From Darrell Stiffler

Do Formal Project Management Practices Lower Costs?

Do Formal Project Management Practices Lower Costs?

Yes. It is cheaper to run a project using formal project management practices than without formal rules and procedures, and the cost of having controls in place is less than the cost of the problems that will develop if there are no controls.

In effect, formalizing the project management process is free. It even saves money. Lots of money.

Not everyone would agree, of course. No doubt there are examples of projects that worked out “just fine” without any fancy rules to control the behavior of the project manager (PM). However, I argue that the cost of success for these projects is being judged by the wrong people.

Who Is Measuring Cost?

When comparing the cost of projects with or without formal project management practices, it is necessary to consider whose perspective is being used. Project managers do not consider costs in the same way that the owners of a project do.

Project managers have “destination fixation.” They perceive success to be the completion of a project, on time and within budget. They want to “get ‘er done!”

Project managers like informal project management practices because they gives PMs the freedom to choose how to fulfill project objectives best.

The problem is that “destination fixation” doesn’t necessarily serve the best interests of the initiating stakeholders (owners).

Formal Project Management Means Stakeholder-Focused

Stakeholders want projects to serve their needs; not merely to come in on time and budget. Building something that doesn’t work, or does not fill the need for which it was intended, is not considered to be successful, even if the project is completed on time and budget. It is an expensive mistake.

Formal project management helps to ensure that projects serve the needs of the initiating stakeholders. It saves money by helping to prevent the perpetuation of projects that are motivated by the priorities of the PM or that are driven by operational necessity rather than stakeholders’ needs.

Formal project management saves more money than it costs, by forcing discipline in the planning and execution phases. This discipline helps to ensure that the project serves the interests of the initiating stakeholders and not of the project manager or team.

Formal project management protects the interests of the owners. It is much cheaper than simply hoping that the project management team will get it right.

From Brian Egan

Photo source

How To Get ‘Urgent’ From Project Team

Ever ask a team member to get something done; one who you can usually count on, and it just does not get done?

How do you elegantly raise the heat to get them to understand the urgency?

“I need this before Thursday, because it has to go out to the customer on Thursday morning. Can you do it?” I said.

“Sure, no problem,” he/she replied.


Well, now it is a problem – it is Thursday morning, it is not on my desk or in my email, and my request has been lost into the ethereal world of hope. Now I am both dismayed and embarrassed as I had promised this would be done by today.

Why am I forced to light a fire under them just to get a simple task done? Why was my urgent request not in their mind? Why would they want me to have to chase them over something so simple?

I realized I forgot to instill in them the fear of failure; look them in the eye and get fully-acknowledged acceptance of the urgency. I failed to put it in writing and remind them the day before .. I should have done it myself ..

Why do I need them if I can do it faster myself?

What do you do with your staff to ensure they understand the urgency of a request?

From David Egan

Image source

Performing Root Cause Analysis on Personnel?

In 1982, Kaoru Ishikawa (1915 – 1989) created the cause and effect diagram also known as the fishbone diagram. The fishbone diagram is often used in root cause analysis to identify linkages between systems or events (parallels can be drawn from the term “root” in root cause analysis and the root of a plant).

young Kaoru Ishikawa

young Kaoru Ishikawa

Identifying issues that are the “cause” can be difficult and time consuming, much like identifying the extent of a plant’s root system. Roots are typically hidden, and the size can’t be determined without digging up the plant completely. Similarly, problems are often not visible, and determining their overall effect on the project without digging into the issue is impossible. It takes a great deal of effort to dig out the root and identify the problem.

It would be difficult to be in the workforce for any length of time without running into the term root cause analysis. The concept is quite simple to understand, however, it can be a challenge to perform and solve. The Rubik’s Cube puzzle is a simple concept as well – also not easy to solve.

Continue reading ‘Performing Root Cause Analysis on Personnel?’

Does “Formal” Project Management Decrease Risk?

Does “Formal” Project Management Decrease Risk?

The short answer is, yes. To understand the question, you need to recall my definition of formal project management. I described it as project management with strict rules. In a formal environment, project managers (PMs) must adhere to guidelines, procedures and practices such as those advocated by the Project Management Institute (PMI). Some PMs would argue that guidelines, procedures and practices just increase cost and lengthen the duration of projects. They suggest that informal project management is more cost effective.

Formal Project Management and Accounting

My counter-argument is based on the parallels between project management and accounting. Every project is like a business. Projects are investments. According to the PMI’s definition, projects are investments that have a unique deliverable. If the deliverable is unique, the organization must lack specific experience in the execution of the project. Of course, how inexperienced the organization is depends on the specific situation.

Stakeholder Perspective

So let us say that you owned the company and that it was your money being invested in a project. How structured would you like the planning and execution to be? Would you let a project that was spending your money proceed without a detailed plan? Or without guidelines and best practices to control execution? I am willing to bet that you would not want to. Informal PMs have the freedom to do what they think is best (i.e., to execute a project the way they want), and they argue that this flexibility is in everyone’s best interest. Investors want to know what is being done by whom, why and when. They want rules, reports and analysis.

Formal Project Management Is Accounting and Accountability

How many businesses operate with informal accounting practices? How many businesses allow staff to spend money as they see fit? Virtually none. Why are accounting practices (money controls) so formal? They are kept formal in order to minimize the risk of money being badly spent; to stop people from spending money according to their own set of priorities. Why should project management practices be formal? 1) To minimize the risk of money and resources being badly spent; 2) To prevent projects from spending money and consuming resources according to unspecified priorities.

Formal project management practices serve the interests of investors (stakeholders) who want to be told in advance how their money and resources will be consumed. Formal project management puts the investors in the driver’s seat. Informal project management relegates investors to the role of spectator. Formal project management does not eliminate risk, but it diminishes risk by keeping stakeholders better informed and more involved and by helping to ensure that resources are being wisely spent.

From Brian Egan

Photo source

Personal Conflict Issues on Teams

A recent discussion with a staff member was mostly a venting of her frustration with her manager. It was just a week before a big event that all the sales teams had been getting ready for, and her manager decided to reshuffle the teams.  Although she and her partner had been one of the top producing teams, each was being reassigned because 2 other staff members were unable to work together.

She did not like being split-up just because the other group members were incapable of working together. She figured it was a stupid management decision to have the best two people re-partnered with two of the younger and much weaker staff members.

“It made no sense, just fire them if they are so incompetent; don’t drag the rest of us down as well,” she said. She had tried to reason with her manager to not do this so close to the event, but the manager had made up her mind, and the decision was final.

Making management decisions is not always popular or pleasant, and the results may be even more unpleasant, as they were in this case. All 4 members were unhappy and unproductive, because they did not really know how to work with their new team members. Was there a better solution?

Carefully consider motivating factors, the ‘Hygiene Factors,’ and the long term benefits when changing team members around. There are always good reasons to try to deal with conflict rather than shifting the combatants around. Check the pulse of your staff regularly, and try to remain objective and positive. Make sure the decision has been well thought-out for all affected team members and is in the interest of the long term goals of the corporation.

If this has happened to you, was it a good decision in the long run?

From David Egan

Photo source


Follow us on Twitter

Author Archives