Failure of Information Technology Projects

Paper Summary:

This paper discusses why nearly seventy-five percent of all information technology (IT) projects are unsuccessful. It looks at how Computerworld and other research typically identify reasons for failure as miscommunication, hazy goals, scope creep, inept leadership, and poor project management. However, it attempts to show that the extraordinary rate of setbacks is also attributable to other fundamental differences that exist between IT and non-IT projects. Beginning with project justification and continuing through planning, staffing, implementation, and quality assurance, it examines how IT projects face more challenges and issues than do non-IT projects.

From the Paper:

"IT projects are subject to many implementation concerns that are not common to non-IT projects. First, long-term projects sometimes lead to systems being delivered for products and services that are longer in the use by the organization. Concepts of incremental delivery don't always work because of data and design interdependencies (Lyytinen and Hirschheim, 1987). And, systems that are rushed to fast delivery often disappoint users because these systems have only a fraction of the facilities that were requested. IT builds systems based on end-user inputs that are vague and change over time. When the system is delivered, business users say it does not do what they requested it to do. Scope creep is also a common phenomenon in IT projects."

More papers on Failure of Information Technology Projects:

• Case Study # 100789 : "Case Study: Information Technology Project Management (ITPM)"
• Analytical Essay # 136711 : "Information Technology in Design and Construction"
• Research Paper # 92437 : "Project Failures"

APA Citation:

MLA Citation: