Five reasons to kill IT projects

Five reasons to kill IT projects By Michael Krigsman, ZDNet Wednesday, December 17, 2008 11:11 AM A recent study highlighted the top five reasons IT experts who killed a project gave for terminating projects prior to completion. Here's some insight on the five. A survey of IT experts revealed 43 percent of their organizations had recently killed an IT project. The study, conducted by ISACA, an independent IT governance group, highlighted the top five reasons these organizations named for terminating projects prior to completion. Here's the list, with my commentary on each issue: 1. Business needs changed: 30 percent There are many conditions and situations where a business legitimately changes its requirements after starting a project. If the project no longer provides meaningful value, then it's best to stop throwing good money after bad. On the other hand, some organizations deliberately obscure a flawed project requirements process by claiming business needs evolved. Read more » Recent Tech Management TechGuides   10 roles you need for ITIL configuration management If you're serious about building an effective configuration management service, you'll need to consider who will accomplish 10 key functions. Here's a brief rundown of the essential roles that should be covered. Wednesday, December 10, 2008 11:25 AM Find more stories in::  IT Management How to prioritize your organization's projects Here are some tips work with management, to successfully determine how to balance new and existing projects. Wednesday, December 03, 2008 02:27 PM Find more stories in::  IT project management, Project management Get a slipping project back on track Plenty of things can derail a project plan--here are some practical techniques that can correct the direction of a project that's losing ground. Wednesday, November 26, 2008 02:16 PM Find more stories in::  IT project management, Project management