Managing Structure-Related Software Project Risk: A New Role for Project Governance

Abstract

This paper extends recent research on the risk implications of software project organization structures by considering how structure-related risk might be managed. Projects, and other organizations involved in projects, are usually structured according to common forms. These organizational entities interact with each other, creating an environment in which risks relating to their structural forms can impact the project and its performance. This source of risk has previously been overlooked in software project research. The nature of the phenomenon is examined and an approach to managing structure-related risk is proposed, responsibility for which is assigned as a new role for project governance. This assignment is necessary because, due to the structural and relational nature of these risks, the project is poorly placed to manage such threats. The paper argues that risk management practices need to be augmented with additional analyses to identify, analyze and assess structural risks to improve project outcomes and the delivery of quality software. The argument is illustrated and initially validated with two project case studies. Implications for research and practice are drawn and directions for future research are suggested, including extending the theory to apply to other organization structures.

Top Fifty Software Risk Factors and the Best Thirty Risk Management Techniques in Software Development Lifecycle for Successful Software Projects

“…According to Ernawati et al (2012), presented framework for software risk management depends on ISO 31000 and it utilizes a designed architecture that includes the basic components of software risk management like risk identification and risk analysis [29]. Furthermore, Bannerman (2010) postulates that risk management approach practices need to be increased with extra analysis so as to identify, analyze and assess structural risks and to mitigate software risks in software projects [30]. Büyüközkan and Ruan (2010) present incorporated multi-criteria to estimate the methodology for software managers to mitigate software risks.…”

Quantitative and Intelligent Risk Models in Risk Management for Constructing Software Development Projects: A Review

“…Today, software risk management has become a common principle and practice amongst leading software companies [30]. In the increasing effort to improve software development processes and software quality, recent studies have pointed out to an area of software project risk [31]. However, many of the software projects are risky and are often considered runaway, because they do not meet the expectations of budgets and schedules.…”

“…al., (2013) proposed the risk management system based on three risk management steps i.e., risk identification, risk reduction and risk control [42]. Furthermore, risk management approach practice need to be increased with extra analysis to identify, analyze and assess structural risks to mitigate software risks and the delivery of software project quality [31].…”

Managing Software Project Risks (Analysis Phase) with Proposed Fuzzy Regression Analysis Modelling Techniques with Fuzzy Concepts

“…This is interpreted as a percentage of 1.33 % from the dependent variable of risk1. According to the fuzzy concepts in multiple regression analysis to produce a fuzzy multiple regression model by solving these equations, the final fuzzy equation is: Table 8 shows that the significant value is less than the assumed value at the  = 0.05 level of significance, so there is a positive relation between controls 1,2,3,4,5,6,7,8,9,10,11,12,16,19,20,28,29,30 and risk 4. Also, controls 3 and 6 have an impact on risk 4.…”