<body>

The A-Z of Project Management Survival

Put that Prince 2 book down, this is the real art of project management and software delivery

All contributors have at least 20 years of successful Project Management and Software Delivery experience, so pay attention.
 

O is for... Ostrich

Thursday, July 26, 2007
StumbleUpon Toolbar
You know the type, you probably have some of them in your organisation; when there's a problem, they bury their head in the sand, usually because it is beyond their capabilities to do anything else.

They will ignore the inevitability of the situation, hoping upon hope that it will go away. Usually until the very last minute, when they will endeavour to get rid of the problem or otherwise attempt to make someone else responsible for their own failure to deliver. This is often too late to do anything effective and even the best endeavour to help out will result in association with the problem.

Best to avoid these people, and if it's impossible to avoid them, or you have a sneaking feeling that the hospital pass will be coming your way at the end of it all, practice a little coaching on them as an exercise in splash damage limitation.

Labels: ,

O is for... Overload (no such thing as)

Tuesday, July 17, 2007
StumbleUpon Toolbar
Here's a simple tip. Never say you are too busy for anything. Because its not true. The real answer is that what you are being asked to do doesn't rank higher in priority than the things you are currently engaged in.

You will hear many people complaining of overload, being too busy, "rushed off my feet". Lame. Because overload doesn't exist. Here's another simple tip. You can only do one thing at a time. So, write down everything you have to do in the best priority order you can do and start at the top. One at a time.

People who say they are too busy generally have three main failings:
  1. They fail to say no.

  2. They fail to delegate.

  3. They fail to adjust priority and expectations when something else goes to the top of the list.

Everyone will always tell you that what they need you to do should be your number 1 priority. Sometimes they will use the word urgent. Often it will be in bold. But there really is no point in taking on 2 or 3 such simultaneous tasks and failing to deliver them all. There is always some give in any ridiculous demand. Try phrases like "OK, I can do X today, but I'll have to drop Y & Z, can you check with Mr. Y and Mr. Z that they will be OK with that?"

You see, faced against other people's real priority items, some demands can look a little daft, so let them find that out in discussion with their colleagues. Means you don't have to tell them, which saves you time.

This is particularly important if its your boss who is asking. You can always deflect this by saying "OK I'll complete that report you never read by the end of the day, but can you let the client/business/whoever know that I won't be able to do [task] for them?"

There is never, ever anything to be gained by taking the weight of the world on your shoulders for delivery by 5pm or else. But similarly, you can't say you are too busy. Because, frankly, that's a crap answer.

Labels: ,

O is for... Optimism

Wednesday, July 11, 2007
StumbleUpon Toolbar
Optimism is reserved for misguided souls and high-level management.

You need to be better than that, you can't sit around and hope it'll all turn out for the best. You'll be dead in the water if you subscribe to such fanciful notions, look around you at all those failed projects.

One thing you need to remember is that you need to make your own luck to be in control your project's destiny. Few bosses hand out gold stars for, it wasn't my fault. Not even McDonalds do that.

Think ahead; put the necessary steps in place to prevent the bad things happening, get the right people (see good-guys) involved to make sure the right things do happen, and when people say you were lucky, that worked out well, you can afford yourself an inward wry smile.

Labels: ,

 
   





© 2007 The A-Z of Project Management Survival.
No part of the content or the blog may be reproduced without prior written permission.