All change again!

My current assignment comes to an end in September.

I'm looking forward to a break, because the last two assignments have been a log slog and I've only had a week off all year.

This current assignment has been one of my most enjoyable, probably because the programme was in such a state when I arrived.

The end client had been promised a lot and had received little. The transformation part of the programme was roughly a year behind schedule, with no signs of delivering much in the near future.

Some people on the programme had to be replaced; they were either getting stale and jaded or they simply weren't up to the challenge.

In some cases, the developers had been asked to achieve the impossible, but it took a change of management for anyone to realise it was impossible and so change the way they were working.

Structurally, the organisation's business model did not lend itself to efficient delivery, because people were not necessarily incentivised to focus on one particular account.

The parlous state of the programme was hidden - not necessarily deliberately - because reporting was very subjective.

My first task was to make the reporting objective, based on the programme schedule. This turned most RAG reports red almost instantly, and people began to understand the scale of the problem. Then, we reorganised the way the account was set up, to incentivise people to focus on the one account.

I also replaced people in key positions, created a whole new programme management team below me and restructured the sub-programmes into outcomes-based projects in order to reduce complexity and risk.

Next, I mandated a better governance structure, based on MSP and PRINCE 2, and increased the size of the PMO. Programme and sub-programme boards were dramatically reduced in terms of the number of attendees so they became proper management forums instead of talking shops, and finally RAID management became effective.

All of this, of course, was done against a backdrop of commercial/contractual "discussions" with a somewhat unhappy and tense end-client.

Things are back on an even keel now, but it has become clear that the programme will take far longer to complete than was ever envisaged. Consequently, I've started replacing contract staff with FTEs to reduce burn rate.

With the programme in a far healthier state and on track to deliver, I can hand over to a permanent Programme Director and look for my next assignment - once I've played a bit of golf of course!

Never underestimate the importance of Stakeholder Engagement

I've always considered stakeholder engagement to be one of the primary skills I bring to the table on any assignment, which was why I volunteered to write the Stakeholder Management section of the upcoming revision of the Association for Project Management's Body of Knowledge.

Stakeholder engagement loomed large on each of the programme rescue assignments I undertook over the last five years, and it's playing a large part in my current role.

People are newly TUPE'd over to a new organisation, and so are understandably nervous and concerned for their futures, even though their futures can be very rosy in the new organisation if they embrace it.

The retained staff too are inevitably struggling to come to terms with the changes. There are new processes for them to learn, they can no longer "call in favours" from colleagues to cut the bureaucratic corners because those colleagues now need a Purchase Order, and some of the retained staff feel that the new outsourcing arrangement is a judgement on their past performance.

Add to the mix the fact that this is quite a political working environment and you can see why careful stakeholder engagement is so important.

Fortunately, I have an excellent programme sponsor, so, whilst my stakeholder engagement skills have brought most people on board with the new proposals, the sponsor's experience in dealing with one or two stragglers has been invaluable.

I'm always careful to remember that:

1. People must be won over
2. Logic alone won't do it
3. Neither will adhering slavishly to a methodology
4. Often the most sceptical once won over become the most evangelical.

Have a good day and keep that "Can do" attitude!

http://www.stevesyder.com

Green Shoots of Recovery?

Maybe the jobs market really is beginning to look up. I'm at least finding more appropriate contracts to apply for this month.

I'm waiting for the result of an interview I had yesterday, and expect to hear today if I have been selected for interview for a second role.

Both opportunities are roles I would relish.

Having said that, I'm not easing up on my search for an assignment; competition is too tough out there to take anything for granted.

When I'm not job hunting I'm now busy working on the Stakeholder Management section of the APM's next edition of the Body of Knowledge (BoK), so at least I'm keeping my brain ticking over.

The Power of the Internet

The internet seems to be an integral part of most people's lives these days. I know that I and most of my friends, family and colleagues are connected to it most of the day.

This gives the worldwide web great power, and sometimes I wonder if that is necessarily a good thing.

My wife and I went away for a golfing weekend last weekend. We booked it through our usual golf trip arranger, so we were confident it would be OK. I then did a bit of research about the hotel at the golf course, and, much to my dismay, I found one very damning review.

The writer clearly felt very strongly, as she had written a very long review, listing a whole catalogue of things wrong with the hotel, not least the lack of hygiene.

In counterbalance to that review, I read many that praised the hotel, its staff, the food etcetera, but needless to say, we arrived at the place somewhat concerned about what we would find.

We need not have worried. It was, as one reviewer said, a place of "faded grandeur", but the cleanliness, size of the rooms and quality of the facilities was absolutely fine.

More than absolutely fine was the service given by every single member of the staff, who were very impressive.

The food was a little mixed, dinner and lunch being very good while breakfast was less impressive.

The only point of agreement I found with the damning review was the poor quality of the mattress, and we were assured that is due for replacement.

So it just goes to show - one damning review could spread like wildfire and damage that hotel for years to come, and yet we had a great weekend.

It takes a long time to build up a good reputation but only moments to build up a bad one. Never was that saying more true than in these internet days.

Association for Project Management

Another good day with the APM last Friday - a feedback session for all those involved in the work we've been doing lately.

Everyone was very positive and things are moving forward at a good pace.

I'm hoping to be involved with the rewrite of the Body of Knowledge, and I should hear about that next month.

I enjoy my work with the APM; everyone is so professional and committed. I'm really looking forward to our project going public towards the end of this year.

Programme Management cf Project Management

(with apologies for the spelling of "Program"!)

http://www.ibm.com/developerworks/rational/library/4751.html

Good Day

Yesterday felt like a really productive day, helping the APM.

I collaborated with some very professional people, and it's good to feel that we are giving something back to programme and project management.

The work is fairly hush-hush at the moment, and I'm frustrated that I can't say more, but when the news is made public it will be very exciting.

For now, I'm back to the mundane, looking for a new programme management assignment, but at least I'm out tonight with wife, son and his girlfriend so I'm looking forward to that.

PMOs

I was recently asked why so many programme and project managers regard PMOs as an unnecessary overhead.

Too many PMO staff, in my experience, seem to think that the main purpose of a programme/project is to produce management artefacts, e.g. Risk Logs, reports etc.

They lose sight of the fact that the PMO is there to help the project achieve success via efficient and effective governance processes.

I worked on one assignment recently where the PMO person allocated to the programme had no concept of what the programme was delivering - despite my best efforts to explain it and have her read the Business Case, Vision etc. - and was simply hell-bent on having the Risk Register updated on a fortnightly basis. It wouldn't have been so bad if she insisted that the risks were actually managed, but it was only the documentation she was interested in!

Once she was removed from the programme we delivered on time and to budget, and our governance satisfied successive OGC Gateway Reviews with no-one from the PMO assigned to the programme.

I've managed other programmes where PMO staff understand that they are there to add value and to help achieve the end-goal, and in those cases they have been a tremendous aid to the programme. It's all about people understanding why good governance matters.

MSP Advanced Practitioner Exam

I'm sitting the MSP Advanced Practitioner Re-registration Exam today.

It doesn't seem like five years since I first attained the qualification, but in these hard times I think it's important to keep your core qualifications current.

The public sector in particular insists on freelance programme managers being MSP qualified, and it's also a useful addition to my Continuing Professional Development Log to maintain my standing within the Association for Project Managers (APM).

I'm confident the exam will go well; I've used MSP in practice solidly since before I qualified, so if I don't know about it by now I never will!