Identification and Quantitative Analysis of Project Success Factors for Large Scale Projects

Identification and Quantitative Analysis of Project Success Factors for Large Scale Projects

Basit Shahzad, Abass Md Said
Copyright: © 2014 |Pages: 13
DOI: 10.4018/ijksr.2014010107
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Software projects require a right mix of the software resources and the expertise to increase the chances of timely completion. The interface for the resource allocation to the software projects is provided by the project factors. The identification of the comprehensive project factors for the diversified nature of projects in itself is an open research area. This paper is based on a quantitative study that helps in identifying the prominent software project factors for large scale projects. The paper then, as a result provides a list of project success factors and provides the statistical evidence to support the result of the survey.
Article Preview
Top

1. Introduction

Software project factors also called project success factors are used as an interface to allocate resource to a software project. A literature study was conducted in this regard to identify the most common project factors. Schoeffel and Pablo (2012) have mentioned that there are only three valuable factors in any successful projects to be considered, cost, effort and quality. The author has also proposes SMART techniques to make a project successful. Nasir et al. (2006a) has stated that there are five factors in estimating the project, namely time, effort, cost, resources and specifications. This authors have also focused on the effective balancing between the cost, time, space, effort and resources. The authors have suggested that an abstract level of estimation as detail bound estimations may lead to wrong results. The author further suggest that an effective balancing mechanism be in place for utilizing the increasing resources as after some increase the resource utilization decreases. For skills the author focus on having the right skills instead of just having the skills to increase the productivity of the teams working on the project.

Schmidt (Schmidt, Lyytinen, Keil, & Cule, 2001a) and Keil (2002) have observed that Requirement change, availability of re-usable code, cost, time and team size are all valuable factors for a software project. Taylor (2006)believes that requirement change, team and time are enough to be considered as the project factors. Hashim et al. (2013) has identified that Computational resources, Requirement change, Time and Team size are the factors to calculate the scale and complexity of the software project. In a report, published by Standish Group (Group, 2012) and Hashimi et al. (2012) it was mentioned that the Computational resources, Requirement change and Team size are sufficient to identify the project estimates while some alike investigations can be found in A. M. S. Basit Shahzad (2012), Iqbal and Shahzad (2006), S. Al-Mudimigh, Ullah, and Shahzad (2010), Shahzad, Al-Mudimigh, and Ullah (2010a), Shahzad and Saqib (2005), and Shahzad, Ullah, and Khan (2009).

Complete Article List

Search this Journal:
Reset
Volume 8: 4 Issues (2017)
Volume 7: 4 Issues (2016)
Volume 6: 4 Issues (2015)
Volume 5: 4 Issues (2014)
Volume 4: 4 Issues (2013)
Volume 3: 4 Issues (2012)
Volume 2: 4 Issues (2011)
Volume 1: 4 Issues (2010)
View Complete Journal Contents Listing