Recipe for project failure

Find below the recipe for project failure from an interesting case study

  • Excessive schedule pressure: Unrealistic project plans
  • Changing needs: Frequent changes / Not following any change control practices
  • Lack of technical specifications: The specifications were not revised as the operational requirements changed.
  • Lack of a documented project artifacts: Knowledge rests with people. If the person leaves you are sunk
  • Excessive innovation: Trying out unwarranted technologies which are not be really required
  • Lack of scientific methods: Not following proven scientific methods in key tasks like estimation (function points), design (UML) etc
  • Ignoring the obvious: Going Live even after performance test results are pathetic 🙂
  • Possible mendacity: Hiding the facts 



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s