Archive for the 'project managment' Category

What project benefits really mean for the project manager

I had a long and protracted email ‘conversation’ with a project manager based in Europe. He was adamant that the prime reason that anyone ran with a project was to deliver benefits. Our email ‘conversation’ went on for some time and we both agreed that there was not enough emphasis put on benefits management and benefits realisation in projects. 

Our emails covered many aspects including what benefits realisation means to the project manager. We finally agreed that at its simplest, it means ensuring project benefits are clearly identified and articulated and realised in projects. 

So, what does this all mean for the project manager? 

  1. Establishing clear project benefits early in the life of the project: these need to be clear and realistic and need to take account of “delusional optimism.” This is over-emphasising projects’ potential benefits and underestimating likely costs, spinning success scenarios while ignoring the likelihood of possible mistakes. (See Defeating ‘Benefits Fraud - Stephen Jenner
  2. Asking questions: easy questions, difficult questions and dumb question of your stakeholders. The project manager needs to tease out the real business benefits. and to do this you need answers to questions; answers your stakeholders will often find difficult to answer. On our project management training courses we talk a lot about developing questioning skills and you may find this  helpful   
  3. Developing clear measurement criteria: too often I hear project managers talking about project benefits they have identified. When challenged there are no measurement criteria against them and no process in place to check that the benefits have been achieved post project. Do remember ‘delusional optimism ‘in point 1 above 
  4. Marketing the benefits: we have had many comments from people on our project management courses  that say something like “we cannot get finance on board” or “HR do not want to buy into this project”. If the benefits were packaged and sold to them effectively then maybe, just maybe they would come on board or buy into the project  
  5. Ensuring benefit management is integrated into your project: is the focus on delivering the project or the project benefits? You may argue they are the same however we have seen people drive delivery without the inclusion of project benefits! Project management benefits are integral to project management, not an ‘add on’ 
  6. Recognising that benefit realisation can be a staged process: if the project is to say save money or improve quality then the project to deliver these may have ended before the savings or the quality improvement are realised. An analysis of project benefits may need to be picked up some months after project closure, maybe it is a project in its own right 
  7. Making recommendations; project managers often complain of not enough resources (time, money, and people). There is pressure to deliver more with less however sometimes the project manager must be able to suggest or recommend to their sponsor that certain projects take priority over others. Rather Why not use clearly identified and measured benefits to help you do this. Compare and contrast one set of benefits against another. Of course, the priority decisions need to be made by classifying project benefits it can help

 There is a clear trend for more emphasis on benefits management. This will mean project managers developing realistic benefits that add real value to projects. Project managers will need to sell benefits to stakeholders including project sponsors and ensure effective monitoring takes place. Don’t forget, a benefit may take some time to be realised so you need to have a process that follows up; often some time later. 

It’s your job to protect project scope

Yes it is. Someone needs to do it, so why not you! Protect the project scope!

Well, there are some major assumptions that need testing in the above words:

  1. someone needs to do it; I am still coming across projects where the scope of the project is identified, agreed but not managed. So, whether you are a project sponsor, project board member, project manager or team member. Take responsibility and protect what has been agreed.
  2. protect the project scope; why bother? I have assumed of course that the scope of work has been agreed. If this is the case then the scope needs protecting. I see too many projects where scope creep seems endemic. (Scope creep, amending the scope of work to be done without an agreed process to check that the ‘new work’ is worth doing)

A lack of protection around the scope is a clear risk. It is also a governance one - who can make the decisions to change the project and how.

So, here is a simple process to help you manage scope creep or requests for change. It is by no means perfect and you will need to put your head above the parapet by suggesting completing of a change request form. Download a brief PowerPoint presentation here and some hard copy documents.

“Scope creep is a sick illness treatable only by saying no.” This quote came from a project manager who decided to challenge the ‘request’ from a senior manager to include something in the project. I suggested he should avoid saying NO but use the process. He did and focused on the process in the presentation and it worked!

Get the presentation here and some free templates!

Does your project get off to a clean start?

The beauty of a 100 meter race is that everyone starts the race together. The race cannot be started without a clean start. Can the same be said of your projects? Does your project get off to a clean start?

Not according to people who come along on our project management training workshops. They say that the start to their project is often haphazard and often poorly managed (if at all). What they do not say but is plain to see is that this poor start up is the cause of many issues that hit project later on. Comments received include:

• I was not even aware this was a project; I was asked to do some work and the next thing I knew I was in a 5 month long project. My boss was far from pleased

• We were like a car with an engine problems; turning over but not getting very far

• I was not clear why we were doing the project

• I was involved but not clear what my role involved

• I was not in favour of doing of doing this project - I queried whether this fitted our strategy and did not receive a response!

Some people have told us that they do have a planned and a structured start and the kick off meeting really helped in ensuring this took place.

Kick off meetings really help focus the minds of people and are vital to get that ‘clean start’. I wonder why there seem to be so few clean starts.

Is this your experience - why not let us all know and the impact this had on projects. 

Project Challenge - free workshops and seminars

How is your diary looking on 30 September and 1 October?

I ask because on those dates “Project Challenge” is taking place at Olympia, London. There are free seminars, presentations alongside an exhibition and of course the inevitable opportunity to network.
Why not go along and take some of your project management colleagues with you? It is a really good opportunity, one not to be missed.

You can find out more by registering on line at www.projectchallenge.com

Do introduce yourself to me if you go along, it would be good to meet up!

Project Management Comment Causes a Stir on Twitter

When you write something it can really come back to bite you. Such was the case on Friday when I wrote a quick Tweet (I think that is what they are called) and dashed out from my office.

Imagine my surprise when I looked on Twitter over the weekend and saw some comments on my Tweet which clearly had caused some people to question what I had written. I wondered why?

It soon became obvious that I needed to write a proper response rather than the 140 Twitter character limit.

So, let me start with the comments I placed in Twitter. I said: “Strict adherence to the project management methodology is more important than delivering the project.”

How did this come about?

The first thing is to point out that it is a quote (not mine!) I was on a train recently and got talking to a couple of people opposite me. They inevitably asked me what I did and explained that we help companies to deliver projects on time, to budget and with the right results. There was a moment of silence, a smile, and they both admitted to being senior project mangers!

We spoke for a while about the project management profession and one of them talked about the project management methodology used in their company. Together they were pretty scathing about the methodology and the above quote was one of my travelling companions, supported by his colleague!

So let me put this event further into context:

• both of the project managers did not believe in the quote; this was the way they saw the company applying it

• I have long believed that methodologies should be pragmatic; I have designed company wide methodologies and applied this approach and it works!

• if a company is serious about delivering its strategic agenda, it needs an overall project management methodology. It need not be complex, simply work for them! It is a guide, not a set of rules

• the business case for a project management methodology is so strong I, and many others cannot understand why many companies do not have a common approach

• the approach is not the only aspect required; strong project management structures, excellent people skills alongside good financial management are also needed plus lots of other aspects

So, the next time I dash off something very quickly, I will check it out ….very carefully and ensure I get my message across effectively.