International Journal of Scientific & Technology Research

Home About Us Scope Editorial Board Blog/Latest News Contact Us
10th percentile
Powered by  Scopus
Scopus coverage:
Nov 2018 to May 2020


IJSTR >> Volume 3- Issue 11, November 2014 Edition

International Journal of Scientific & Technology Research  
International Journal of Scientific & Technology Research

Website: http://www.ijstr.org

ISSN 2277-8616

Evaluation Of PMI’s Risk Management Framework And Major Causes Of Software Development Failure In Software Industry

[Full Text]



Kamran Khan, Salman Qadri, Shabir Ahmad, Abu Buker Siddique, Anam Ayoub, Shaista Saeed



Index Terms: Software Project Risk, Project Management Institute, Software Industry, Structural Equation Modeling



Abstract: To reduce the high failure rate of software projects, managers need better tools to assess and manage software project risk. As a way to build such resources, on the other hand, details programs analysts must remainder create a better knowledge of the particular measurements of software package project risk as well as how they may have an impact on task performance. Development in this area continues to be obstructed by means of: (1) a reduction in confirmed equipment intended for computing software package project risk that will make use of the particular measurements of chance which have been seen as essential by means of software package task supervisors, as well as (2) a reduction in idea to describe the particular linkages in between numerous measurements of software package project risk as well as task performance. Within this examine, six to eight measurements of software package project risk ended up recognized as well as reliable as well as logical measures ended up designed for each and every. Well guided by means of socio techie programs idea, an exploratory model originated as well as analyzed. The outcomes present that will societal subsystem chance influences techie subsystem chance, which often, in return, influences how much task supervision chance, as well as eventually, task performance. This significance of those information intended for investigation as well as exercise are usually reviewed.



[1] Gordon, P. (1999, January 18). To err is human, to estimate, divine. Information Week, 65—72.

[2] Barki, H., Rivard, S., & Talbot, J. (1993). Toward an assessment of software development risk. Journal of Management Information Systems, 10(2), 203— 225.

[3] Boehm, B. W. (1991). Software risk management: Principles and practices. IEEE Software, 8(1), 32—41.

[4] Charette, R. N. (1989). Software engineering risk analysis and management. New York: Intertext.

[5] McFarlan, F. W. (1981). Portfolio approach to information systems. Harvard Business Review, 59(5), 142—150.

[6] Keil, M., Cule, P., Lyytinen, K., &Schmidt, R. (1998). A framework for identifying software project risks. Communications of the ACM, 41(11), 76—83.

[7] Azam, Farooq, et al. "Framework Of Software Cost Estimation By Using Object Orientated Design Approach."

[8] Arrow, K. (1970). Essays in the theory of risk-bearing. Amsterdam: North-Holland. Bagozzi, R. P., & Phillips, L. W. (1982). Representing and testing organizational theories: A holistic construal. Administrative Science Quarterly, 27, 459— 489.

[9] March, J. G., &Shapira, Z. (1987).Managerial perspectives on risk and risk taking Management Science, 33(11), 1404—1418.

[10] Ahmad, Shabir, and Bilal Ehsan. "The Cloud Computing Security Secure User Authentication Technique (Multi Level Authentication)."

[11] Karolak, D. W. (1996). Software engineering risk management. Los Alamitos, CA: IEEE Computer Society Press.

[12] Casher, J. D. (1984).How to control risk and effectively reduce the chance of failure Management Review, 73(6), 50—54.

[13] Jiang, J. J., &Klein, G. (2001). Information system success as impacted by risks and development strategies. IEEE Transactions on Engineering Management, 48(1), 46—55.

[14] Hatcher, L. (1994).A step-by-step approach to using the SAS system for factor analysis and structural equation modeling. Cary, NC: SAS Institute.

[15] Nidumolu, S. R. (1996). A comparison of the structural contingency and risk-based perspectives on coordination in software-development projects. Journal of Management Information Systems, 13(2), 77—113.

[16] Thayer, R. H., Pyster, A., & Wood, R. C. (1980).The challenge of software engineering project management. IEEE Computer (August), 51—59.

[17] Baloch, Muhammad Perbat, et al. "Comparative Study of Risk Management in Centralized and Distributed Software Development Environment." Sci.Int.(Lahore), 26(4), 1523-1528, 2014.