After effects of a Massive Tech Project Failure in IT

Thomas Walgum discusses  about several after effects of a failed IT project as suggested by Chris Curran, partner and CTO of Diamond Management & Technology Consultants. He discusses about various causes of project failures such as perfect expectations about completion of a project, inefficient segmentation of massive projects and not embracing transparency. The effects of a project failure on the CIO of organization are elaborately discussed.

According to the author, IT is not totally to be blamed when a project fails because the business side also plays its part. Because IT projects are considered “technology projects”, when a project fails the blame is totally usually thrown in that direction. The CIO is one who frequently suffers more from an IT project that does not succeed. He is usually relegated from his position and if it’s a massive project it becomes nearly impossible for him to recover. The business executives are usually not accounted for a project failure. He draws this conclusion from a survey of numerous IT professionals.

One way an IT project can prevent failure is to divide huge projects to small chunks which makes tracking progress easier. Setting proper expectations, changing implementation methods when needed, embracing transparency in the organization are also important for a successful project.

References:

Wailgum, T. (2009, August 5). After a Massive Tech Project Failure: What IT Can Expect. Retrieved from http://www.cio.com/article/499047/After_a_Massive_Tech_Project_Failure_What_IT_Can_Expect