You think everything is fine with the project you are working on and then something derails it! It happens all the time, yet it always seems to catch us by surprise. It's hard enough just trying to execute on a project, much less worry about what could derail it. However, it seems worthwhile to contemplate what could go wrong and perhaps anticipate potential remediation attempts. Here are my top 10 ways your project could get derailed, in true David Letterman style.

10. Requirements keep changing. This is one of my personal favorites. Requirements are set at the beginning of the project; everyone knows what needs to be delivered. Then users say, "Couldn't we just add this functionality that we really need? It would make the whole system so much more powerful!" Yes, and the project manager gets lessons in how to balance requests for changing requirements with the need to actually complete the project.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access