Saturday, June 20, 2009

Ten ways to sink an IT project

During the recent Project Management Institute (PMI) congress from last May, Andre Chrome made an interesting show about ten ways to sink your project. And of course it applies perfectly to any IT project and I modified them sightly for this purpose.

  1. Be vague: Do not define any detailed scope that would force you to implement what you promised.

  2. Begin the execution ASAP. Why make a planning when you already know lots of changes will happen.

  3. Focus solely on your team. Clients will only interfere with your work.

  4. Forgot about code documentation and instead prefer mutual trust with your client.

  5. Go beyond your client expectations. As clients expect always more and fancy features, you will sign new contracts that will compensate for your losses and bugs.

  6. Risk management ? By definition, risk is uncertain. Why bother planning for risk.

  7. Quality is only important at the end of the project. The client will only look at the GUI anyway.

  8. Avoid bureaucracy. Paperwork is a waste of (your) time.

  9. Make sure your team works overtime. As IT project are overdue anyway, put pressure on your team from the start.

  10. Throw away paper documents when the project is over. Paper files takes place in your office and none ever read them.

Here is the video of this presentation:

No comments: