The paper identifies and ranks the risks affecting the software projects globally. This study is based on 12 researches which have been conducted in different parts of the world. The results of the study have also been shared with some senior IT professionals working in Noida. Based on their inputs, the paper also reveals that the top five risks identified in this study have important linkages amongst them and their management is crucial for the success of the project
AddisonTVallabhS (2002), “Controlling software project risks: An empirical study of methods used by experienced project managers”, Proceedings of SAICSIT 2002, September, port Elizabeth, pp. 128–140.
2.
AroraAArunachalamVSAsundiJFernandesR (2001), “The Indian software services industry”, Research Policy, Vol. 30 (8), pp. 1267–1287.
3.
BoehmB (1991), “Software risk management principles and practices”, IEEE SoftwareVol. 8 (1), pp. 32–41.
4.
BoehmBWDeMarcoT (1997), “Software Risk management”, IEEE SoftwareVol. 14(3), pp. 17–19.
5.
BrooksFP (1995), The Mythical Man-month: Essays on Software Engineering, Addison Wesley Longman, United States.
6.
CostaHRBarrosMDOTravassosGH (2006), “Evaluating software project portfolio risks”, Journal of Systems and software, Vol. 80, pp. 16–31.
7.
FieldT (1997), “When BAD things Happen to GOOD projects”, CIO, pp. 55–62.
8.
JiangJKleinG (1998), “Systems analysis attitude toward information systems development”, Information Resource Management Journal, Vol. 11(4), pp. 5–10.
9.
JiangJKleinG (2001), “Software project risks and development focus”, Project management Journal, Vol. 32(1), pp. 20–26.
10.
KeilMCulePLyytinenKSchmidtR (1998), “A framework for identifying software project risks”, Communications of the ACM, Vol. 41(11), pp. 76–83.
11.
KeilMSmithJPawlowskiSJinL (2004), “Why didn't somebody tell me? Climate, information asymmetry, and bad new about troubled projects”, DATABASE for advance in Information Systems, Vol. 35(2), pp. 65–84.
12.
KwakYHStoddardJ (2004), “Project risk management: lessons learned from software development environment”, Technovation, Vol. 24, pp. 915–920.
NaKSSimpsonJTLiXSinghTKimKY (2007), “Software development risk and project performance measurement: Evidence in Korea”, The Journal of systems and software, Vol. 80, pp. 596–605.
15.
OzESosikJ (2000), “Why information systems projects are abandoned: a leadership and communication theory and exploratory study”, Journal of Computer Information Systems, Fall, pp. 66–78.
16.
RaiAKeilMCheneyJEZhangGP (2003), “Why software projects escalate: the importance of projects”, management constructs”, IEEE Transaction on Engineering Management, Vol. 50(3), pp. 251–261.
17.
SchmidtRLyytinenKKeilMCuleP (2001), “Identifying software project risks: An international Delphi study”, Journal of Management Information Systems, Vol. 17(4), pp. 5–36.
18.
ShererSA (1995), “The Three dimensions of software risk: Technical, Organisational, and Environmental”, Presented in 28th Annual Hawaii International conference on system sciences, pp. 369–378.
19.
SmithDEastcroftMMahmoodNRodeH (2006), “Risk factors affecting software projects in South Africa”, South African Journal of Business Management, Vol. 3(2), pp. 55–65.
TiwanaAKeilM (2006), “Functionality Risk in Information Systems Development: An empirical investigation”, IEEE Transaction on Engineering Management, Vol. 53(3), pp. 412–425.
22.
YongHJuhuaCZhenbangRMeiLXieK (2006), “A Neural Networks Approach for Software Risk Analysis”, Sixth IEEE International Conference on Data Mining-Workshops (ICDMW'06).
