In software projects, often, risk handling capacities have a determinant power w. r. t. ensuring project efficiency. They can make or mar project efficiency. In this paper, an incremental risk management framework is presented. A unique sample risk management template with example is proposed to capture the modification. The revision to the existing risk management framework also captures inputs and outputs at every stage of risk management process. Together with these two, dashboard or graphical user interface (GUI) or web user interface (UI) is designed for ease-of-use and to build a work habit where risk management team members, developers, leads and managers must be able to state software or hardware risks at every stage of risk management process. The new framework maintains a repository to manage a central risk log which is at the center of spiral model; i. e. after every crucial step recording in repository takes place. The data and previous documentation from repository serve as input for the next step. As risk factors w. r. t. software configuration management is affected by the modification, a case study is presented w. r. t. how including version information in risk templates can be remedial for the software(s/w) risks involved.

1. Charu Verma and Saad Ali Amin. "Significance of Healthy Organizational Culture for Superior Risk Management during Software Development", IEEE Conf. on Developments in E-systems Engineering (DESE 2010), 6-8 Sep. 2010. London, UK. pp. 182 – 189.
2. Edzreena Edza Odzaly, Des Greer and Paul Sage, "Software Risk Management Barriers: an Empirical Study", Third International Symposium on Empirical Software Engineering and Measurement (ESEM 2009), China. 15-16 Oct. 2009, FL U. S. A. pp. 418 – 421.
3. Engr. Shehnila Zardari, "Software Risk Management", International Conference on Information Management and Engineering, 3-5 Apr. 2009. Malaysia. pp. 375 – 379.
4. Hooman Hoodat and Hassan Rashidi, "Classification and Analysis of Risks in Software Engineering", World Academy of Science Engineering and Technology 2009, pp. 446-452.
5. IAN Sommerville. "Software Engineering: Risk Management", 7th Edition. Print.
6. Martin Boldt, Bengt Carlsson and Roy Martinsson. "Software Vulnerability Assessment Version Extraction and Verification", International Conference on Software Engineering Advances(ICSEA 2007), 25-31 Aug. 2007. France, pp. 59-65.
7. M. M. Sharma, Prakriti Trivedi, Anil K. Dubey, Akanksha Toshniwal and Himanshu Swarnkar. "Pioneering an Automated Risk Removal Tools in Software Engineering", International Conference on Information Systems and Computer Networks (ISCON), 9-10 March 2013, India. pp: 104-107.
8. Puspamitra Mishra, Nabarun Roy, Balamukund S, Rajni M S, Shilpi Jain and Jude Fernandez. "A Risk Framework for New Country Compliance for Global Software Companies", Seventh International Conference on Global Software Engineering Workshops 27-30 Aug. 2012, Brazil. pp: 1-5.
9. Rogger S Pressman. "Software Engineering: Risk Management", 6th Edition. Print.
10. Zhang Jun-guang and Xu Zhen-chao. "Method Study of Software Project Risk Management", International Conference on Computer Application and System Modeling (ICCASM 2010), China. 22-24 Oct. 2010. V8-9 - V8-12.

Software Risk Management (rm) Risk Template Risk Repository Dashboard Roles & Responsibilities Software Configuration Management (scm) Version Control And Incremental Risk Management Framework.