Core Factors for Software Projects Success

Mohammad Ibraigheeth - Universiti Sultan Zainal Abidin, Kuala Terengganu, Malaysia
Syed Fadzli - Universiti Sultan Zainal Abidin, Kuala Terengganu, Malaysia


Citation Format:



DOI: http://dx.doi.org/10.30630/joiv.3.1.217

Abstract


The successful software project can be defined as the project that meets the planned quality, cost, schedule, and effort. It has been suggested that there are many reasons which might lead to software project success.  Several success and failure factors for particular projects were discussed in the literature. This paper aims to identify the most common success factors through reviewing a set of software project reports and case studies. In order to fully understand reasons behind the project success, the reasons behind project failure and the definition of failure itself are discussed. Furthermore, case studies of successful and failed software projects are described. This paper also investigates techniques that have been developed to increase software project success rate and decrease probable failures.

Keywords


software project success; success factors; software project failure; project performance; success rate.

Full Text:

PDF

References


Standish, G. (1994). The chaos report. The Standish Group.

Lewis, J. P. (2000). Project planning, scheduling and control. McGraw-Hill Companies.

Linberg, K. R. (1999). Software developer perceptions about software project failure: a case study. Journal of Systems and Software, 49(2-3), 177-192.

Hastie, S., & Wojewoda, S. (2015). Standish group 2015 chaos report-q&a with jennifer lynch. Retrieved, 1(15), 2016.

Robbins-Gioia, L. L. C. (2002). ERP survey results point to need for higher implementation success.

Chowdhury, R., Butler, R. E., & Clarke, S. (2007). Healthcare IT project failure: A systems perspective. Journal of Cases on Information Technology (JCIT), 9(4), 1-15.

Whittaker, B. (1999). What went wrong? Unsuccessful information technology projects. Information Management & Computer Security, 7(1), 23-30.

Charette, R. N. (2005). Why software fails. IEEE spectrum, 42(9), 36.

Dalcher, D., & Brodie, L. (2007). Successful IT projects. Cengage Learning EMEA.

Flowers, S. (1997). Software Failures: Management Failure: Amazing Stories and Cautionary Tales. London: John Wiley & Sons.

Tan, S. (2011). How to Increase Your IT Project Success Rate. Gartner Research.

The Standish Group. (2013). The Chaos Manifesto.The Standish Group.

GAO Report (12-7). (2011). Information Technology: Critical Factors Underlying Successful Major Acquisitions, GAO. Washington, D.C.: Government Accountability Office.

GAO Report (14-705T). (2014). Preliminary Results of Undercover Testing of Enrollment Controls for Health Care Coverage and Consumer Subsidies Provided Under the Act

Verner, J., Sampson, J., &Cerpa, N. (2008, June). What factors lead to software project failure?.In Research Challenges in Information Science, 2008.RCIS 2008. Second International Conference on (pp. 71-80). IEEE.

Ewusi-Mensah, K. (2003). Software Development Failures: Anatomy of Abandoned Projects. Cambridge: MIT Press

Devos, J., Van Landeghem, H., & Deschoolmeester, D. (2008). Outsourced information systems failures in SMEs: a multiple case study. Electronic Journal of Information System Evaluation, 11(2), 73-84.

Nelson, R. R. (2005). Project retrospectives: Evaluating project success, failure, and everything in between. MIS Quarterly Executive, 4(3), 361-372.

Dalal, S., & Chhillar, R. S. (2012). Case studies of most common and severe types of software system failure. International Journal of Advanced Research in Computer Science and Software Engineering, 2(8).

Al-Yaseen, H., & Al-jaghoub, S. (2012). Success and failure of e-learning projects: alignment of vision and reality, change and culture.

www.Reksoft.com

www.calleam.com

Stanciu, V., & Tinca, A. (2013). ERP solutions between success and failure. Accounting and Management Information Systems, 12(4), 626-649.

Devos, J., Van Landeghem, H., & Deschoolmeester, D. (2008). Outsourced information systems failures in SMEs: a multiple case study. Electronic Journal of Information System Evaluation, 11(2), 73-84.

Wende, E., & Philip, T. (2011, January). Instant messenger in offshore outsourced software development projects: experiences from a case study. In System Sciences (HICSS), 2011 44th Hawaii International Conference on (pp. 1-10). IEEE.

Cole, A. (1995). Runaway projects: cause and effects. Software World, 26(3), 3-5.

Takagi, Y., Mizuno, O., &Kikuno, T. (2005). An empirical approach to characterizing risky software projects based on logistic regression analysis. Empirical Software Engineering, 10(4), 495-515.

Reyes, F., Cerpa, N., Candia-Véjar, A., & Bardeen, M. (2011). The optimization of success probability for software projects using genetic algorithms. Journal of Systems and Software, 84(5), 775-785.

Wang, X., Wu, C., & Ma, L. (2010, July).Software project schedule variance prediction using Bayesian Network.In Advanced Management Science (ICAMS), 2010 IEEE International Conference on (Vol. 2, pp. 26-30).IEEE.

Lehtinen, T. O., Mäntylä, M. V., Vanhanen, J., Itkonen, J., &Lassenius, C. (2014). Perceived causes of software project failures–an analysis of their relationships. Information and Software Technology, 56(6), 623-643.

Dalal, S., & Chhillar, R. S. (2012). Case studies of most common and severe types of software system failure. International Journal of Advanced Research in Computer Science and Software Engineering, 2(8).

http://calleam.com

Reyes, F., Cerpa, N., Candia-Véjar, A., & Bardeen, M. (2011). The optimization of success probability for software projects using genetic algorithms. Journal of Systems and Software, 84(5), 775-785.