Project Failure is Fun!
Written by Stuart Easton
10 Reasons Projects Fail
Number 10 - Poor scope management.
Number 9 - Poor stakeholder communication
You know what you're doing, but perhaps there are others who should also be in the loop to avoid... accidents.
Number 8 - Projects You Should Never Have Attempted
We've all done this. The business logic appeared sound, but there was just too much unmanaged risk!
Number 7 - Poor Change Management
You've seen this one before... the project is moving along at a rapid pace, but the stakeholders just aren't ready for you to roll it out...
Number 6 - Poor Project Planning
So many failed projects could be avoided by simply thinking ahead... something this young man needs to learn!
Number 5 - Poor Communication
Between teams, within teams, between individuals... poor communication wrecks projects.
Ouch!
Number 4 - Wrong Person, Wrong Place
The wrong person with the wrong skill-set can derail a project quicker than most people can spell hiippoput.... hipapot.... hippopotamouse.... hippopotamus!
Number 3 - Lack of Exec Support
I've written before about how a lack executive support can break your project. This is often because the projects you're working on aren't aligned to what's strategically important... so the exec sponsor's mind wanders.
This one deserves everything he got!
Number 2 - Juggling too Many Things
Okay, I know I bang on about this all the time, but trying to do too many projects is a real project killer. This guy was lucky to get away with just an orange in the face!
Time for some serious project prioritization.
Number 1 - Poor Risk Management
The risk register is one of the key tools of project management but it is often misused.
Which can hurt...