Risk Management in Agile Software Methods
DOI:
https://doi.org/10.59992/IJCI.2024.v3n7p2Keywords:
Risk Management, Agile Software Methods, extreme Programming, Software ToolsAbstract
Project risk is the problems, which have not happened yet, that could cause some loss or threaten the success of the project, whereas risk management is the application of appropriate tools and procedures to contain risk within acceptable limits. Risk management is the application of appropriate tools and procedures to contain risk within acceptable limits. In this paper, the authors apply risk management to software development that uses extreme programming approach. A risk tool is designed and developed using Microsoft Excel. The tool is simple to use and would help risk analysis of the twelve practices of extreme programming. The tool has been used and experimented with. Information such as project budget, risk management budget, cost of controls, SLE, ARO have been entered into the tool to analyze the priority practices in order to decide which practice must be dealt with first.
References
[1] Assassa, G., Mathkour, H., Al Dossari, H. (2006), ‘Extreme programming: A case study in software engineering courses’, Proceedings of the 1st National Information Technology Symposium, NITS, Riyadh, Saudi Arabia, pp. 233-240.
[2] Cameron, J. W. (2004), Managing Risk Across the Public Sector, The Victorian Auditor-General’s Office, pp.1-8.
[3] Crystalball (2007), http://www.crystalball.com
[4] Kent Beck (2004), Extreme Programming Explained: Embrace Change, 2nd ed., Addison-Wesley, MA.
[5] Master Solutions Ltd. (2000), http://www.riskease.com/index.html
[6] Mathkour, Hassan, Aboalsamh, Hatim, Assassa, G., Al Dossari, H. (2006), ‘Use of Extreme programming in software engineering Education: A pilot Study’, The Engineering research Journal, Minoufia University, Vol. 31, No. 1, 2008, pp. 39-48.
[7] Misic, V.B. (2005), Perceptions of Extreme Programming: A Pilot Study. IEEE International Engineering Management Conference Proceedings, Volume 1, Issue Sept. 11-13, pp. 307-312.
[8] Paul Oldfield, Hüseyin Angay and Dan Rawsthorne, (2002), Risk to Pattern Table, Appropriate Process Movement, white paper, pp. 1-9. http://www.aptprocess.com/whitepapers/risk/RiskToPatternTable.htm
[9] PertMaster Project analytics (2008), http://www.pertmaster.com
[10] Ramachandra, P., Kim, H.K., Kang, B., Ha, Y., Lee, R. (2006), Risk Management through Architecture Design, IEEE Fourth International Conference on Software Engineering Research, Management and Applications (SERA'06), pp. 386-395.
[11] Risk Management Policy Document (2005), Charnwood & Northwest Leicestershire PCT Risk Management Policy No. H&S/CNWL/1/5/8, 2005/2006, pp.1-42.
[12] RiskTrak, International (2007), http://www.risktrak.com/rstdemo.htm
[13] Shodan Input Metric Survey (2005), http://c2.com/cgi/wiki?ShodanInputMetric
[14] Sommerville, I. (2004), Software Engineering, 7th edn, Addison-Wesley, New York.
[15] [15] Stewart Hayes BSA (2004), Software Tools for Risk Analysis and Management, pp.1-18.
[16] Sugianto, M. S. (2002), Risk Management In Project Management, The University Of Queensland Brisbane, Australia, pp. 32-61.
[17] Tsui, F. (2004), Managing Software Projects, Jones and Bartlett, London, pp. 107-122.
[18] Vanguard Software Corporation (2008), Management Systems for the Intelligent Enterprise. http://www.vanguardsw.com
[19] Wiegers, K. E. (1998), Know Your Enemy: Software Risk Management, Software Development magazine, October, pp. 1-6.
