Characterization of risky projects based on project managers evaluation

During the process of software development, senior managers often find indications that projects are risky and take appropriate actions to recover them from this dangerous status. If senior managers fail to detect such risks, it is possible that such projects may collapse completely. In this paper, we propose a new scheme for the characterization of risky projects based on an evaluation by the project manager. In order to acquire the relevant data to make such an assessment, we first designed a questionnaire from five view-points within the projects: requirements, estimations, team organization, planning capability and project management activities. Each of these viewpoints consisted of a number of concrete questions. We then analyzed the responses to the questionnaires as provided by project managers by applying a logistic regression analysis. That is, we determined the coefficients of the logistic model from a set of the questionnaire responses. The experimental results using actual project data in Company A showed that 27 projects out of 32 were predicted correctly. Thus we would expect that the proposed characterizing scheme is the first step toward predicting which projects are risky at an early phase of the development.

[1]  Victor R. Basili,et al.  Developing Interpretable Models with Optimized Set Reduction for Identifying High-Risk Software Components , 1993, IEEE Trans. Software Eng..

[2]  Shari Lawrence Pfleeger,et al.  Software metrics (2nd ed.): a rigorous and practical approach , 1997 .

[3]  Taghi M. Khoshgoftaar,et al.  The Detection of Fault-Prone Programs , 1992, IEEE Trans. Software Eng..

[4]  Watts S. Humphrey,et al.  A discipline for software engineering , 2012, Series in software engineering.

[5]  Yasunari Takagi,et al.  Analyzing effects of cost estimation accuracy on quality and productivity , 1998, Proceedings of the 20th International Conference on Software Engineering.

[6]  Dale W. Karolak Software Engineering Risk Management: Finding Your Path through the Jungle , 1998 .

[7]  Mariet Labuschagne,et al.  RISK MANAGEMENT IN SOFTWARE DEVELOPMENT , 2000 .

[8]  Dale Karolak,et al.  Software engineering risk management , 1995 .

[9]  Shinji Kusumoto,et al.  Improvement of Software Process by Process Description and Benefit Estimation , 1995, 1995 17th International Conference on Software Engineering.

[10]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[11]  Victor R. Basili,et al.  A validation of object oriented metrics as quality indicators , 1996 .

[12]  Edward Edward Yourdon,et al.  Death March: The Complete Software Developer's Guide to Surviving Mission Impossible Projects , 1999 .

[13]  Edmund H. Conrow,et al.  Implementing Risk Management on Software Intensive Projects , 1997, IEEE Softw..

[14]  Victor R. Basili,et al.  A Validation of Object-Oriented Design Metrics as Quality Indicators , 1996, IEEE Trans. Software Eng..

[15]  Frank J. Sisti,et al.  Software Risk Evaluation Method Version 1.0. , 1994 .

[16]  Shinji Kusumoto,et al.  Analysis of review's effectiveness based on software metrics , 1995, Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95.

[17]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.