What is “Success” in Project Management?

Your client’s perception of project “success” is the basis from which your client concludes, for example, whether the project of high quality, that money paid to you was well spent, that you did a good job as a consultant, and whether you might be hired again (if you are an external consultant). Early in the project, it is important for you and your client to discuss how to determine the success of the project.

Unfortunately, determining whether a project was successful or not is not nearly as easy as it might seem because there are numerous perspectives on what is project “success.” Therefore, it is important to consider all of these perspectives, especially about a complex – and usually changing – project. Consider the following possible definitions of what might be considered as “success” in your consulting project, and work with your client to select one or more.

1. Desired outcomes and results listed in the project agreement are achieved?

Both you and your client should somehow specify the overall results that the project is to achieve. Ideally, the results are described in terms such that you both could readily discern if the results were achieved or not. This outcome is often a measure as to whether the project was successful or not.

2. The client’s problem is solved?

More times than people realize, the originally specified project results have little to do with actually solving the most important problem in your client’s organization. That occurs because, as you and your client work together to examine and address their overall problem, you both realize that there is a more important problem to address. At that time, it is wise to change your project plans if both of you agree. Discuss the new results that you prefer and how you will know whether or not they are achieved.

Still, later on, your client might believe that any agreed-to results that were achieved from the project were not as important as addressing any current, unsolved problems, so your client might still conclude that the project was not as successful as it should have been. Or, your client might believe that any achieved results were actually more useful than addressing the original problem that you discussed, so your client might still conclude that the project was highly successful.

3. The project is finished on time and within budget?

Often, your client has limited resources in terms of money and time. Therefore, any project that did not require more time and money than expected might be considered successful. That might be true, especially if your client has the philosophy that there are always problems to be solved in any organization and that the project was done as best as could be done.

4. You and your client sustain a high-quality, working relationship?

The quality of your relationship with your client is often directly associated with what the client perceives to be the quality of the project. In a highly collaborative approach to consulting, you want your relationship with your client to be as open, honest and trusting as possible. The nature of the relationship supports your client’s strong, ongoing commitment and participation in the project itself, which, in turn, helps to ensure that the project effectively addresses problems in their organization.

5. Your client learns to address similar problems by themselves in the future?

This outcome should be one of the major goals for any consultant. However, the exact nature of the problem may never arise in the client’s organization again, so it is often difficult to assess if the client has learned to solve that problem. Also, few consultants are willing to scope a project to the time required to assess whether a client really can solve the same type of problem in the future.

6. Your client says that they would hire you again (if you are an external consultant)?

One of the most powerful outcomes is that you both are willing to work with each other again. One of the ethical considerations for any consultant is to avoid creating a dependency of the client on the consultant – where the client cannot capably participate in the organization without the ongoing services of the consultant. However, it is not uncommon that the client strongly believes that the quality of the relationship with the consultant is as important as the consultant’s expertise. The client might choose to use that consultant wherever and whenever they can in the future.

7. You get paid in full?

This perspective might sound rather trite. However, you might feel good about the quality and progress of a project only to conclude, later on, if you have not been paid as promised, that the project was not successful.

What do you think?

—————————

For more resources, see the Library topic Project Management.

———————————————————————————————–
Carter McNamara, MBA, PhD – Authenticity Consulting, LLC – 800-971-2250
Read my weekly blogs: Boards, Consulting and OD, Nonprofits and Strategic Planning.

Procurement and projects – best and worst practice?

The following is definitely not at the “best” end.

I recently had to respond to a bid for major customer – in the customer ITT the usual procurement rules were laid down. The ITT had been written in English; by someone who’s native tongue was not. The document was full of inconsistencies, incomplete or vague and conflicting statements.

In the procurement rules in the ITT, it stated that: “no meetings or verbal discussions would take place with any of the bidders” – all communication would done in writing, and it got worse, in one single pass. In other words, no clarification on the customer’s response to bidders questions would be entertained, and from this, the bidders were expected to present binding fixed price bids.

Sadly, in the world of procurement, this is not an isolated case.

Many projects rely completely on procurement, but too often the project team’s decisions or needs are overruled by the procurement process or function – and the end result? The project has to try and fix the issues that this leaves behind or generates – and sometimes they can’t be fixed.

Surely there has to be a better way?

—————————

For more resources, see the Library topic Project Management.

—————————

Organisation and projects:

There are many elements in the environment of a project, and ‘organisation’ is one of the most important. Organisational decisions can encompass wide-ranging aspects, such as partnerships, key supplier and sub-contracting relationships and responsibilities within a project – and that’s the key word: “responsibilities”.

Making responsibilities clear at the practical working level, perhaps phase by phase, is one of the most important tasks a project team will do. The converse is that if we don’t make responsibilities clear, the downstream impact of this will all too often be measured in cost, schedule and technical terms – sometimes this alone leads to substantial impacts on a project’s success and delivery goals.

So, if this is the case, why is it that so many project teams roll along without spending much effort or paying attention to this question – it seems such a fundamental thing to do, but corporate and individual behaviour does not always support this?

What do you think and what are your experiences on your projects?

—————————

For more resources, see the Library topic Project Management.

—————————

Being a project manager means

there will be times when you will not be the most popular person in the room ……

Much of the lot of the project manager is concerned with dealing with issues; that may mean bringing attention to issues, their source, impact and resolution to the table for the project team, sponsors and executives to resolve. In these circumstances, project mangers need to be: open; ruthlessly objective; focused; and visionary. Not every individual would relish this responsibility, for example, in a recent conversation with wanna-be project managers, many practical examples of issues that PMs may face were discussed – not everyone in the room was happy about being responsible for managing their resolution and what this would entail in real life.

Testing issues such as this should be an important element of selecting project managers as well as defining their responsibilities.

—————————

For more resources, see the Library topic Project Management.

—————————

Being a PM doesn’t mean I have to chase people on tasks, does it?

As with many walks of life, there are many views on project management. The following short discussion demonstrates brilliantly the differing views of people relating to the task of project management and the responsbilities of a project manager.

When having met an organisation recently I was talking to a few project managers, and one of them said to me: “being a Project Manager doesn’t mean I have to chase people on their tasks does it” (to provide some context, this was a relatively small firm with small project teams – less than 6 key people in each project team).

It’s an interesting question as on this alone you get completely different behaviours (and processes) among Project Managers, and resulting from this alone you can get very different results from projects.

Let us know your thoughts on this question?

—————————

For more resources, see the Library topic Project Management.

—————————

PM Certification – does it make a difference?

Certification programmes in vocational qualifications have exploded in the past 10 years or so, and the project management world is no different.

In the US, the Project Management Institute’s “PMP” qualification probably leads to way. In the UK we have a similar qualifications from our own “Association of Project Management”, for example “APMP” – we also have Prince2 qualifications, which is primarily the UK Government’s project management methodology.

But here’s my question: do you think that having a certificated project manager makes a real difference to the project or otherwise?

Let us know your thoughts?

—————————

For more resources, see the Library topic Project Management.

—————————

Ethics in project management – customers and suppliers?

Picking up on Ethics in PM – dealing with customers – for example, how soon do you tell the sponsor / customer about an issue and what information do you give them?

We all know what should ideally happen; customers and suppliers should have access to and exchange real, timely information on aspects such as progress, risks and issues on projects.

However, we all know what happens in practice too often – information is massaged, withheld and provided in limited forms, as parties exchange information on projects.

What is your experience?

—————————

For more resources, see the Library topic Project Management.

—————————

The role (and challenge) of the project sponsor

many firms today are trying to introduce and use the role of sponsor on projects. Executed well, this role can contribute hugely to making a project a success in delivery terms and especially the outcomes that projects are intended to deliver.

The challenge is:

  • To deliver the role they need to be fairly senior people – often they are very hard to get hold of
  • They often don’t have a background in projects (or a project management process), leading to a lack of appreciation of the role and the value of elements of the process
  • It’s simply assumed by the organisation that any senior person can deliver this role
  • They sometimes shy away from the most important responsibilities of a sponsor

What’s your experience and tips if you have any?

—————————

For more resources, see the Library topic Project Management.

—————————

Real Responsibilities of Project Managers?

Too many businesses describe the responsibilities of a project manager along the lines of: “to deliver the project on time and within budget” – this is the goal of project management, not the responsibilities of a project manager. Neither, for example, does it do much to help those entering the profession to understand the fullness of the role (or the level of challenge they may be about to face).

If you agree with the above, here’s one suggestion: organisations, business schools and the like understand common causes of project failure. Often this includes things like: “lack of / poor planning”. Therefore, if for example, you believe in the value of planning, one line on the PMs responsibilities should focus on this, hopefully qualified by measurable ‘standards’ that the organisation expects to achieve in this or any other area.

The other issue that the opening statement does not help with is the managing effectively the expectations or even behaviours required of project managers. Being an effective project manager requires being willing to take responsibility – not for everything, but in the main for the success or otherwise of the project. Food for thought.

—————————

For more resources, see the Library topic Project Management.

————————————————————————

Kevin Lonergan with Project Management Informed Solutions helps clients improve capability to deliver projects and programs, by providing process assets and skills transfer.

In-House Project Managers vs. External

I have been having an ongoing discussion with a global company that has been having big issues in delivering its major customer projects. They are looking to develop a strategy for provision of real project managers / and or professional project management expertise to help. In doing this, they are having an important debate:

Should they develop in-house local project management competence or should they buy it in as required?

Personally I have my views but what do you think? ”

—————————

For more resources, see the Library topic Project Management.

————————————————————————

Kevin Lonergan with Project Management Informed Solutions helps clients improve capability to deliver projects and programs, by providing process assets and skills transfer.