communication Archives - Project Management Knowledge

Project Management – Dealing with Doomed Projects

Posted on May 21, 2011
1 comment

Most of us hate to admit that things aren’t working out as planned. But, if you are in project management long enough, you will get to experience a project cancellation. Sometimes, you can tell early on that a project has the potential to go very wrong. Warning signs include:

Lack of ownership at the highest level of the organization
Inadequate resources committed at the start of the project
Team infighting and poor communication
Going over budget with no clear timeline for completion
Constant delays in completing schedule milestones
Scope and final goal keep changing

Those final 3 issues can usually be avoided with appropriate planning. However, sometimes you inherit a project from a previous PM that’s already halfway down the road to nowhere. In that case, there’s good news and bad news. The bad news is that you will have to work twice as hard to breathe life back into the project (if that’s even possible). The good news is that you can blame everything that’s gone wrong so far on your predecessor. You can do this without sounding whiny if you offer real solutions to the problems you point out.

What If You Can’t Save a Project?

If obstacles such as high costs, poor design or execution, and changing objectives can’t be overcome or worked around, it may be best to shut things down. This is a time when your project management communication skills need to be at their best. A cancelled project can affect morale throughout your organization. Be sure to solicit input from your full team and other stakeholders before moving forward with shutting down a project. That way, you will all be in agreement and you won’t overlook any possible solutions that could save the project.

Follow Proper Cancellation Protocol

Keeping relationships intact and conserving resources are the two main priorities in the actual cancellation process. If you are performing the project for a client, they should be involved at each step so they don’t feel like it is all out of their control. If you need to cancel orders with vendors, do this as soon as possible so they aren’t devoting production capacity to your project and counting on revenue that’s not going to materialize. When possible, identify ways to reuse project resources for other scheduled or future projects. Be sure to still recognize and reward team members for their contributions – it’s usually not their fault that things went wrong.

Add a Kill Switch in Advance Next Time

One part of project management planning that doesn’t get a lot of attention is setting parameters that will determine when a project should be shut down. This concept should be evaluated during risk management planning. You should be able to identify a specific point when the ROI for a project just isn’t going to be worth it. This could be a dollar amount. Or, it could be a timeline. For example, your organization’s goal might be to bring a certain product or service to market before a competitor. If you fall 12 months behind, the whole project might become moot. Rerouting project resources to something that’s more likely to be a “winner” could be the most strategic choice.

Don’t Get Caught Up in Emotions

Determining the criteria for discontinuing a project ahead of time (and sticking to it) makes it easier to actually pull the trigger if the time comes. Otherwise, you may get caught up in a cycle of justifying more and more expenditures on a project that’s a money pit. Like the song says “You’ve got to know when to hold ‘em, know when to fold ‘em”. Getting emotionally involved in a project and having your pride hurt when you have to let go can be tough. But the sooner you put a failure behind you, the sooner you can start working on your next success.

Filed under: UncategorizedTagged with: communication, planning, project management

Agile Techniques That Mesh With Traditional Project Management

Posted on February 19, 2011
Leave a comment

Agile project management is an iterative approach that focuses on achieving project objectives in distinct stages. It is typically used in the software development industry but has some applications in other fields as well. When the overall scope and specific deliverables are likely to change throughout the lifecycle of a project, an agile approach can make it easier to keep moving forward. This methodology is often best suited for use with small to mid-sized projects. For large scale projects with well-defined deliverables and a high degree of complexity, the agile approach tends to be less useful. However, this doesn’t mean certain features from the agile “toolbox” can’t still be used.

Learn as You Go

You might consider a blended approach that involves traditional waterfall and agile methods. For example, regular meetings that include a review of all lessons learned in the previous week are a core feature of agile project management that can be incorporated into many projects. Since stakeholder feedback is a key factor in compiling lessons learned, the project’s communication management plan must include a way to collect this feedback on an ongoing basis. So, this is an ideal option for projects that involve a client who likes a very “hands on” role.

Quality Takes Center Stage

The agile method also relies heavily on quality control at each stage (since software must be tested and debugged). This is another area where PMs in traditional industries would do well to pay attention. Project quality management should be designed to monitor project deliverables at crucial junctures. Let’s say component B’s performance is predicated on the quality of component A. To avoid delays and increased costs, a quality check should be performed during or immediately after the schedule activity that results in the completion of component A. This type of quality assurance plan can be developed based on an activity sequencing diagram.

Adaptation Requires Flexibility

No matter how thoroughly you plan, there will always be issues that require change requests. With an agile attitude, your team doesn’t have to view these as setbacks. Instead, each modification to the project plan can be seen as an opportunity for brainstorming and problem solving. A project management team that learns to collaborate is more likely to increase the value of a project through creative solutions rather than simply suggesting stop-gap measure to keep the whole thing from falling apart. To make this work, a leadership style that focuses on developing team members rather than simply issuing instructions is essential. In the long run, companies that feature a collaborative environment are almost certain to outperform their competition. So, this is one aspect of the agile method that should be adopted by all businesses that want to remain viable in today’s marketplace.

Filed under: UncategorizedTagged with: communication, lessons learned, planning, project management, quality

Managing People When You’re Not A “People” Person

Posted on January 22, 2011
Leave a comment

As a PM, you know that project management almost always involves a lot of “people management”. However, not every effective project manager has a particularly charismatic personality. For example, you might be a great strategist, highly focused, patient, organized, self-disciplined, and determined to succeed. These are all qualities that go into making a good PM. One important attribute missing from that list is “likability”. That’s because you don’t really need to be a people person to do your job well. What you do have to be is a good communicator. People skills are called “skills” for a reason. They are something you can learn – you don’t have to be born with this talent.

Perception is Reality

If you tend to run into problems with people responding negatively to you, there are steps you can take to change this. You won’t need to transform your personality either. You just need to alter how people perceive you. That’s about communicating the best aspects of yourself – your strengths rather than your weaknesses.

For example, if you tend to be a very literal person, you may have difficulty understanding what people are really saying when they beat around the bush. This may give you a reputation for being a poor listener (if you make mistaken assumptions about what people mean). Or, you could be thought of as brusque if you tell people to “just get to the point already!” Using communication skills such as reflective listening allows you to clarify what’s being said while making the other person feel valued and respected. Then, you get the information you need and they come away thinking you’re a great manager to work with.

Different Strokes for Different Folks

Every individual has a different communication style. However, these tend to fall into one of a few categories. An assessment program such as DISC can help you learn to recognize these behavioral patterns in yourself and in others (Dominant, Influential, Steady, and Conscientious). This is very helpful when you are managing a large, diverse project management team.

For example, a Dominant person may want to address factual issues relating to a project rather than focusing on how a particular decision makes others feel. An Influential individual responds when you start out with friendly conversation before giving instructions for a particular task. A Steady person appreciates being given clear objectives to accomplish on a project. Conscientious people should receive early warning of any upcoming changes to scheduling or procedures so they have time to adjust.

What Can You Expect?

The benefits of learning people skills extend into every aspect of project management. You will know that you are building your ability in this area when:

You experience fewer misunderstandings with all groups of project stakeholders
Team members ask plenty of questions and participate fully in meetings
You find out quickly whenever a problem crops up
Peers and superiors follow your recommendations more frequently
Subordinates carry out schedule activities more effectively with fewer errors and delays

Filed under: UncategorizedTagged with: communication, project management

Why Project Management Ethics Matter

Posted on January 8, 2011
Leave a comment

In project management, having a reputation for doing the right thing is essential for getting your job done effectively. Without trust, communication grinds to a halt. That’s one reason the PMI and other professional business organizations seek to define the values that support ethical work and outline standards of conduct they expect their members to live up to. The term “ethics” covers a lot of territory, but there are some core elements that tend to be included in any discussion of this topic. These include:

Reliability – being trustworthy and honest – acting with integrity

Responsibility – holding oneself and others accountable – striving for excellence

Respectfulness – treating others professionally as one would want to be treated

Fairness – being evenhanded, objective, and consistent in interactions with others

Credentialed project management professionals generally adhere to an ethical code of conduct to maintain their credibility within their field. However, it is also important to acknowledge that there is a great deal of pressure placed on PMs to disregard ethics. When faced with unrealistic deadlines, an inadequate budget, excessive restrictions, or other hindrances to project completion, it can become tempting to stretch the boundaries of ethical behavior.

Here’s an Example:

Sometimes disclosing a particular piece of information would bring down a hailstorm of trouble from stakeholders. It might be possible to avoid all that unpleasantness by leaving a critical bit of data out of a report – at least until you have time to try to fix the problem. Some people would say that’s not really lying, just controlling the flow of information. But if you’ve made a commitment to communicate fully and honestly with your stakeholders (a key component of the PMI code of conduct), it is a serious breach of ethics to withhold pertinent information.

There are Plenty of Opportunities to Get Things Wrong

There are dozens of other ways to cut corners during project management that can make your job seem easier. This includes letting things slide in QA assuming you can go back and fix things later. Or, it might be the temptation to play fast and loose with documentation or regulations due to time constraints. Perhaps you have access to confidential information that could be used to “grease the wheels” with a contractor but that you know you shouldn’t disclose. Conflicts of interest are always a temptation when you are in the position to give and receive favors in the context of a project.

How Important is Your Career?

Then, there may be the threat hanging over your head that if you don’t get the job done your employer or client will find someone else who is willing to do whatever it takes. In fact, from one standpoint, being known as someone who bends the rules to get things done can be a distinct advantage in project management – in the short term. Stakeholders may be happy to look the other way as long as they enjoy a profit as a result of a “successfully” completed project.

However, unethical behavior has a habit of coming to light. It may not rise to the level of criminal misconduct, but it can tank a career regardless. Even in a culture that places a great deal of trust in contracts and in the power of the legal system to enforce them, no one really wants to have to worry about whether they will end up in court when they engage with your organization. When vendors, partners, lenders, customers, employees, and other stakeholders can’t trust the word of a project manager, business relationships break down.

PMs Can’t Afford to Ignore Ethics

Ultimately, a project manager who can’t be trusted will eventually be viewed as a liability by the same people who pushed for the PM to break the rules in the first place. An unethical PM is one who faces a bleak future with not even the comfort of having their self respect intact. In the final analysis, the personal and professional price that is paid for ditching ethics just isn’t worth it.

Filed under: UncategorizedTagged with: communication, ethics, project management

Can You Delegate Stakeholder Management?

Posted on December 29, 2010
Leave a comment

As a busy project manager, the more tasks you can delegate to skilled subordinates, the better job you can do handling the responsibilities that are left on your plate. However, there are some project management functions that don’t lend themselves to delegation. That’s not always because someone else can’t do them. Occasionally, it’s because of the perception it would create if you don’t put in the “face time” in certain aspects of the job. In general, stakeholder management is one of the areas where you have to visibly take charge. Otherwise, you may be perceived as:

A poor communicator
Someone who doesn’t want to take responsibility
Unavailable or unapproachable

In U.S. culture in particular, companies may be expected to have an “open door” policy that makes managers accessible. It is particularly important for stakeholders outside the company to have a consistent point of contact with someone who is viewed as being able to get things done. Clients, vendors, lenders, and partner organizations need to know that their concerns about a project are being taken seriously.

PMs Shouldn’t Shield Themselves Too Much

Excessive use of “gate keeping” that prevents stakeholders from communicating with a project manager directly may cause unnecessary escalation of issues that might otherwise have been easy to resolve. What type of access stakeholders will have to the project manager should be decided as part of communications planning. For example, all mid to high level stakeholders may need to be provided direct contact information (email address and phone numbers) for the project manager. That way, they can bypass perceived red tape in the process of resolving issues.

Having a policy in place of responding to stakeholders within 24 business hours is a good practice in project management. This doesn’t mean the problem has to be resolved immediately; but a discussion should be initiated as soon as possible to avoid delays in the project schedule. The responsibility for actually fixing a problem can certainly be delegated as long as accountability is maintained. An action-item log should be created to document and manage the resolution of issues. This permits the project manager to:

Clarify the issue with a focus on the solution
Assign the responsibility for resolution to a team member
Set a target date for closure
Follow up to ensure the issue is resolved

Internal, Low Level Stakeholders

Managing communication with internal, low level stakeholders often requires a slightly different approach. There may be situations when stepping in to fix a problem actually undermines the authority of your direct reports. Generally, it helps team cohesion for team members to resolve non-critical issues on their own. Overdependence on leadership in project management can negatively affect both productivity and worker satisfaction. So, team members should be encouraged to take responsibility for fixing problems within the scope of their authority and ability (without breaking any company rules).

This type of internal delegation works best when team members all have a good grasp of the “big picture” and the critical objectives of the project as a whole. That way, they can rely on common sense in differentiating between an easily fixable problem and a crisis. Team members should always document any issue and the steps they take to resolve it so this information is available later if needed. The communication management plan should identify a chain of command for who will handle any problems that escalate beyond the ability of lower level staff to resolve.

Filed under: UncategorizedTagged with: communication, project management, stakeholders, team

Tag: communication