Case study: factors for early prediction of software development success
Introduction
Despite extensive research into successful software development [2], [8], [24], [26], many software development projects are still failing [15]. Research into software development is likely to continue until we have the development process under better control [8], [15], [16], [26]. In 1994, 31% of all corporate software development projects resulted in cancellation [8]. A more recent study found that 20% of software projects failed, and that 46% experienced cost and schedule overruns or significantly reduced functionality [15]. Another study suggested that failure rates for software development projects are as high as 85% [11]. Clearly, systems development projects can present serious risks to the well being of an organization [15]. Troubled projects can, for example, cause developers to suffer long hours of unpaid overtime, loss of motivation, and burnout, leading to excessive staff turnover and its associated costs.
Recent research that focuses on factors contributing to the failure of information systems projects usually takes a practitioner point of view (such as that of an IT manager, project manager or software developer) [7], [9], [14], [24]. Management also has a view of what constitutes a successful project and, in some cases, this view is different from that of the project manager and developers, while users may take another quite different view. (Note that when we refer to management, we are referring to corporate management; where appropriate, we will explicitly refer to a project manager.)
The major factors that contribute to the success or failure of software systems fall into seven categories: (1) management, (2) customers and users, (3) requirements, (4) estimation, and scheduling, (5) the project manager, (6) the software development process, and (7) development personnel [7], [15], [20], [22]. Our research investigates some of the most influential success factors early in the development process from a developer's perspective. Successful software development projects are commonly cited as having met agreed upon business objectives, and having been completed on time and within budget [12], [14], [19], [25]. Other definitions of success, include the degree to which the project achieved its goals; reliable, maintainable and met the requirements of users; user satisfaction; effective project teamwork and professional satisfaction on the part of the project manager [10], [21]; and the extent to which the software is actually used [4], [6]. Glass [9] noted a profound difference of opinion between managers and team members concerning software project success, and our recent research agrees with his view [23]. Management tends to consider a project a success if it is delivered on time, within budget and meets specified business objectives [25]. In contrast, developers are more likely to perceive a project to be a success whether it is ‘completed or canceled’ [15]. In a study of several projects, the only criteria for success that had strong agreement among all the involved parties, were ‘meets user requirements, achieves purpose, meets time scale, meets budget, happy users, and meets quality’ [14]. Glass [7] suggests that problems arising from expectations established at the outset of a project have a greater influence on a developer's perception of success and failure than what happens during project development. For developers, a successful project is one in which the product works the way it is supposed to work, their participation provides a technical challenge and a learning experience that develops new skills [15]. Developers also appreciate when a project's cost and schedule are comparable to normal industry standards, which should mean that excessive unpaid overtime will not be required [15]. On the other hand, developers perception of project failure can include unrealistic schedule expectations, lack of resources, and poor understanding of the project's scope at the outset [15].
Insight into early project factors likely to threaten project success will help project managers and other stakeholders to better predict the likelihood of their project's success. This will allow for corrective action early in the development process. This study is a first step towards the establishment of guidelines for project risk prioritization and mitigation in the early phases of software development. Because of the number of generic risks the project manager has to contend with, we wish to provide a severity roadmap showing the consequences of early project actions (taken or imposed). In addition, we will explore the developer's view of factors that impact project success; a successful project manager needs to be aware of success and failure factors from all stakeholder viewpoints, and to be able to respond to these perceptions, either directly or indirectly, in a timely manner [13]. We anticipate that results of this study (and other studies) will be incorporated into a project management decision support tool.
Section snippets
Background
The Standish Group's widely cited research [25] reveals the relative importance of management support, user involvement and requirements for successful project development. In fact, these three software development factors emerge as reoccurring risks.
- •
Management support. Inadequate management practices have far reaching implications for successful software development [1]. A project needs a committed sponsor or champion throughout. This sponsor should participate in the decision-making process
Our investigation
In late 1999, we engaged in structured discussions with 21 IT professionals, including developers, technical support personal, project leaders and project managers (referred to in the body of this paper as ‘respondents’ or ‘developers’), from a large financial institution. Our discussions focused on the issues within their organization that they identified as associated with software project success and failure. Based on these discussions, we developed a questionnaire that targeted software
Results
We received data from 21 developers, reflecting 42 software development (rather than maintenance) projects. While in normal research terms this number of developers and projects is not large, it is a significant number when we consider that they are all from the same organization and that this research reports an organizational case study. The average number of full-time developers working on the projects was eleven (minimum of one and maximum 80) with an average of five contractors and/or
Discussion and conclusions
This study leads us to a number of conclusions about project success from the perspective of developers and their perception of management and project success. We found that developers are very critical of the projects that they worked on and considered fewer projects successful (44%) than they thought management did (77%). We also found various aspects of development that we assumed would be important to developer's perception of success, but proved to lack statistical significance (based on
Lessons learned
One of the most compelling reasons to measure the perceptions of those involved with software development is that participant perceptions of project success, consistent or not with reality, can dramatically affect the health of a project manager, a project team, and thus the health of the project. There is a vast difference between developers' perceptions of project success factors, and their perceptions of how management view the same factors.
What do developers consider is important to
References (26)
Evolving a new theory of project success
Communications of The ACM
(1999)Software developer perceptions about software project failure: a study
The Journal of Systems and Software
(1999)- et al.
In the 25 years since the mythical man-month what have we learned about project management?
Information and Software Technology
(1999) - et al.
When is user involvement not user involvement
Information Strategy: The Executive's Journal
(1997) Software Engineering Economics
(1981)User involvement: key to success
IEEE Software
(1998)Perceived usefulness, perceived ease of use and user acceptance of information technology
MIS Quarterly
(1989)- et al.
Peopleware: Productive Projects and Teams
(1999) - et al.
The Relative importance of perceived ease-of-use in IS adoption: a study of e-commerce adoption
JAIS
(2000) Software Runaways
(1998)
How not to prepare for a consulting assignment and other ugly consultancy truths
Communications of The ACM
Study: 85% of IT departments fail to meet business needs
Computerworld
Cited by (113)
Calculating completeness of software project scope definition
2018, Information and Software TechnologyImplementing Success Management in an IT project
2018, Procedia Computer ScienceLoCo CoCo: Automatically constructing coordination and communication networks from model-based systems engineering data
2017, Information and Software TechnologyA survey on the characteristics of projects with success in delivering client benefits
2016, Information and Software TechnologyCitation Excerpt :In any case, it is well documented that the software industry has a substantial proportion of software projects that are not fully successful. Numerous empirical studies and reviews exist on factors believed to contribute to a software project's success, see for example [20-26]. These studies typically point to perceived success factors related to collaboration with and competence of the client, team skills, change and scope management processes, management support, planning and budgeting.
A deep intelligent framework for software risk prediction using improved firefly optimization
2023, Neural Computing and Applications