Article Preview
Top1. Introduction
In a recent study, the top ten risk factors in a software development lifecycle were studies (Montini et al., 2014) and in a following study the most common software project success factors were also identified (Shahzad, Al-Mudimigh, & Ullah, 2010). The process of identification spans over the literature survey that spans across the valuable literature available in the domain. Until recently, the authors were in a race to identify more and more risk factors. It was believed that more identification can cause better cure against the risks as many researchers have put their efforts to identify software risks (Addison & Vallabh, 2002; Basit Shahzad, Abas Md Said, & Aziz, June 2014; Han & Huang, 2007; Mathkour, Shahzad, & Al-Wakeel, 2011; Pare, Sicotte, Jaana, & Girouard, 2008; Schmidt, Lyytinen, Keil, & Cule, 2001). The statement is true to the level that risks should be known but over emphasis on risk management that it cuts the actual development to size can't be appreciated by any means and in any circumstances. In recent past the prioritization of the risk factors has been done (Shahzad & Iqbal, 2007) and a comprehensive list has been prepared recently (Montini et al., 2014). Following risk factors were identified.
The risk factors presented in Table 1 are an outcome of the literary investigation and prioritization technique by assigning weights which are governed by the frequency of occurrence of the individual factors. A survey based methodology is considered to validate the outcome of the risk factors as shown in Table 1.
Table 1. List of top 10 risk factors (Montini et al., 2014; Shahzad & Al-Mudimigh, 2010; Shahzad, Tanvir, & Irfan, 2005)
Ranking | Risk Factor |
1 | Requirement understanding issues |
2 | Consistently Changing scope |
3 | Lack of management commitment |
4 | Improper budget and schedule estimates |
5 | Lack of skills in project personnel |
6 | Developing the wrong software functions |
7 | Lack of frozen requirements |
8 | Lack of project management skills |
9 | Un-stable user involvement |
10 | Weak project management methodology |