Page 126 - Navy Journal 219

Navy Journal 2019

In other way, risk is defined as a state or property of a development task or
environment, which, if ignored, will increase the likelihood of project failure
(Ropponen & Lyytinen, 2000). Likewise software development risk can be
measured identifying those items recognized as the pitfalls of software
development. In order to identify these pitfalls, the idea of ‘Software Risk
Management (RM)’ comes into play. Software risk management is not yet fully
articulated disciplines, its contribution to date have helped many software
projects avoid divesting pitfalls and reach successful conclusion. In simplest
form, software RM is defined as “an attempt to formalize risk oriented correlates
of success into a readily applicable set of principles and practices (Boehm,
Software Risk Management: Principles and Practices, 1991)”. It aims to use
techniques and guidelines to identify, analyze, and tackle software risk items. In
present time, the study of software risk management involves the understanding
of two facets, namely the risk management practices and environmental
contingencies.
Figure 3. Software Risk Management Research Model

COMPONENTS OF SOFTWARE
DEVELOPMENT RISKS

Risk Management Practices
+ Methods
+ Resources
+ Extent and Period of Use Environmental Contingencies
+ Organizational Environment (O)
+ Technologies (T)
+ Individual Characteristics (I)

Source: Ropponen, J., & Lyytinen, K. (2000). Components of Software Development Risk: How
to Address Them? A project Manager Survey. IEEE Transactions on Software Engineering,
Vol.26. No.2 , 98-111.

118