Why did your project fail?

Author:

Cerpa Narciso1,Verner June M.2

Affiliation:

1. Universidad de Talca, Chile

2. University of New South Wales, Sydney, Australia

Abstract

Introduction We have been developing software since the 1960s but still have not learned enough to ensure that our software development projects are successful. Boehm 2 suggested that realistic schedule and budgets together with a continuing steam of requirements changes are high risk factors. The Standish Group in 1994 noted that approximately 31% of corporate software development projects were cancelled before completion and 53% were challenged and cost 180% above their original estimate. 13 Glass discussed 16 project disasters. 5 He found that the failed projects he reviewed were mostly huge and that the failure factors were not just management factors but also included technical factors. Linberg in 1999 found that 20% of software projects failed, and that 46% experienced cost and schedule overruns or significantly reduced functionality. 8 Later, Glass revisited failed projects and found that poor estimation was high on his list of failure factors. 6 In 2007 the Standish Group reported that 35% of software projects started in 2006 were successful compared with only 16% in the corresponding 1994 report; however, the 2007 CHAOS report still identifies 46% (53% in 1994) of software projects as challenged (having cost or time overruns or not fully meeting user's requirements) and 19% (31% in 1994) as outright failures. 12 The validity of the Standish Group findings has been questioned as not consistent with cost overrun results of other surveys. 7 Jørgensen and Moløkken-Østvold suggested that there are serious problems with the way the Standish Group conducted their research and that the findings were biased toward reports of failure because a random sample of top IT executives was asked to share failure stories when mailed confidential surveys. Recently Charette 4 commented that "billions of dollars are wasted each year on failed software projects" and that "we have a dismal history of projects that have gone awry." 4 Charette suggests that from 5%-15% of projects will be abandoned before or shortly after delivery as hopelessly inadequate. 4 Other recent studies, suggest various failure rates for software development projects up to 85%. 7 Stories of software failure capture public attention and in general there is a perception that software quality is not improving but getting worse. Developing software systems is an expensive, and often a difficult process. Although there are many guidelines for successful software development, 9,11 few project post-mortems are conducted, and little understanding is gained from the results of past projects. The project manager (PM) and the development team must deal with many pressures from project stakeholders (for example, upper level management, marketing, accounting, customers, and users) during the software development process. These pressures impact both the cost and the quality of the software produced. There are generally more than one or two reasons for a software project to fail, and it usually is a combination of technical, project management and business decisions. Many software project failure factors have been described in the literature. 1-13 However, most organizations do not see preventing failure as an urgent matter. It is not understood why this attitude persists. 4 Because most of the literature is based on a handful of failed project case studies, in our research we analyze 70 failed software projects to determine those practices that affected project outcome. We are interested in providing, from the perspective of software practitioners, quantitative evidence targeting those aspects of the development process that contribute to project failure. Essentially, we are interested in updating the results of prior studies and testing the validity of previously reported anecdotal evidence. To date, no one has taken a set of project data and teased it out to identify, for a whole group of such projects, the most common failure factors. We are interested in everyday projects that are not high profile enough to be reported in the literature. Our work builds on that previously reported by Boehm, 2 Charette, 4 Glass, 5,6 Jørgensen and Moløkken, 7 Linberg, 8 and the Standish Group, 12,13 among others.

Publisher

Association for Computing Machinery (ACM)

Subject

General Computer Science

Reference13 articles.

1. Software risk management: principles and practices

2. Why software fails [software failure

3. Glass R. L. Software Runaways. Prentice-Hall New York 1998. Glass R. L. Software Runaways . Prentice-Hall New York 1998.

Cited by 123 articles. 订阅此论文施引文献 订阅此论文施引文献,注册后可以免费订阅5篇论文的施引文献,订阅后可以查看论文全部施引文献

1. Enhancing Agile Story Point Estimation: Integrating Deep Learning, Machine Learning, and Natural Language Processing with SBERT and Gradient Boosted Trees;Applied Sciences;2024-08-19

2. Hard and soft governance mechanisms for large projects. A historical perspective;Journal of Management History;2024-05-03

3. SERGE – Serious Game for the Education of Risk Management in Software Project Management;Proceedings of the 46th International Conference on Software Engineering: Software Engineering Education and Training;2024-04-14

4. Investigating Cultural Dispersion: on the Role of Cultural Differences in Software Development Teams;Proceedings of the 2024 IEEE/ACM 46th International Conference on Software Engineering: Companion Proceedings;2024-04-14

5. Dealing With Cultural Dispersion: a Novel Theoretical Framework for Software Engineering Research and Practice;Proceedings of the 46th International Conference on Software Engineering: Software Engineering in Society;2024-04-14

同舟云学术

1.学者识别学者识别

2.学术分析学术分析

3.人才评估人才评估

"同舟云学术"是以全球学者为主线,采集、加工和组织学术论文而形成的新型学术文献查询和分析系统,可以对全球学者进行文献检索和人才价值评估。用户可以通过关注某些学科领域的顶尖人物而持续追踪该领域的学科进展和研究前沿。经过近期的数据扩容,当前同舟云学术共收录了国内外主流学术期刊6万余种,收集的期刊论文及会议论文总量共计约1.5亿篇,并以每天添加12000余篇中外论文的速度递增。我们也可以为用户提供个性化、定制化的学者数据。欢迎来电咨询!咨询电话:010-8811{复制后删除}0370

www.globalauthorid.com

TOP

Copyright © 2019-2024 北京同舟云网络信息技术有限公司
京公网安备11010802033243号  京ICP备18003416号-3