KEYWORDS
Software Project Risk Assessment, Risk Matrix, Software Engineering
INTRODUCTIONAs indicated by researches [1] [2][3], the worldwide software business sector is evaluated to have an estimation of US$330 billion in 2014. Further, the Chaos Report from the Standish Group reported that the success rate of worldwide (fundamentally U.S. and Europe) software projects in 2015 is only 29% [4].In all projects, risks should be identified, assessed by its probability of occurrence and impact, and a contingency plan should be developed for remediating the problem actually occur [5]. The procedure of risk identification can be troublesome and misleading in some cases. Moreover, knowing whether a risk is important or not is also is another issue which requires more research on cases.This research`s aim is to assess the initial rating of risks for small to medium size software projects. One can see that in recent years, there are not as much studies to determine general risk factors and their possible effects on small to medium size software projects. In order to identify general risks and deploy a survey and obtain rating from practitioners, previous researches in risk assessment and management field had to be reviewed. Some of these studies are briefly given below.Zardari [6] in his research about managing software risks, attempts to provide practitioners with necessary basic information regarding the management of risks in software. The research defines the term of proactive and reactive management, a list of top risks, probability and impact and their levels alongside other terms.Keshlaf [7] specifically focuses on web and distributed software development project risks in this study, and provides a summarized risk set from other works. The research studies risks and challenges in the field and also studies and analysis existing methods and frameworks of software One of the problems with previous studies is that each adopt a sets of risk factors which are sometimes completely disjoint or overlapping. Also most of the studies consider a limited set of risks, therefore we aim to put a wide coverage list of software related risks. We ask software practitioners for their experience over of these risks and study the result to generate a super set of risks and ratings for reference.In our study, by conducting a survey, we mean to distinguish and provide a wider coverage of initial rating to software general project risks and their relations especially for practitioner of small organizations. A top risk list, highly cross correlated risks are provided for use by software teams or practitioners with relatively little experience and previous historical data. The identified wider coverage of general risks and ratings may be used in further studies. Furthermore, we discuss the outcomes and compare our results to other results from a survey of previous works [8].
GENERAL SOFTWARE PROJECT RISK FACTOR COLLECTIONAlthough, in previous studies diverse risk factors, categories and analysis tools have been utilized, in this ...