International Journal of Computer Science & Network Security

International Journal of Computer Science & Network Security (국제컴퓨터통신보호논문지학회)
권호 표지
DOI QR코드

DOI QR Code

Agile Risk Mitigation Framework

  • Received : 2021.12.05
  • Published : 2021.12.30
Download PDF
⟨ Previous Next ⟩

Abstract

Software organisations follow different methodologies for the development of software. The software development methodologies are mainly divided into two categories, including plan-driven and agile development. To attain project success, it is very significant to consider risk management during whole project. Agile development is considered risk-driven, but many risks are unreported at the industrial level. The risks can be divided into three categories, including (i) development risks, (ii) organisations risks, and (iii) people-oriented risks. This paper deals with Development risks specifically. Several risks related to development are faced by people working in the industry while dealing with agile development. Their management among the industry is a big issue, so this paper emphasises ARMF based on development-related risks by following agile development. This research work will help software organisations to prevent different project-related risks during agile development. The risks are elicited at two-level, (i) literature-based and (ii) IT industry based. A systematic literature review was performed for eliciting the agile risks from the literature. Detailed case studies and survey research methods were applied for eliciting risks from IT industry. Finally, we merged the agile development risks from literature with standard industrial risks. Hence, we established an agile risk mitigation framework ARMF based on agile development and present a groundwork established in light of empirical examination for extending it in future research.

Keywords

References

  1. Causevic, A., Sundmark, D., & Punnekkat, S. (2011, March). Factors limiting industrial adoption of test driven development: A systematic review. In Software Testing, Verification and Validation (ICST), 2011 IEEE Fourth International Conference on (pp. 337-346). IEEE.
  2. Mingshu Li, Meng Huang, Fengdi Shu, and Juan Li. A Risk-Driven Method for eXtreme Programming Release Planning.ICSE28thInternational Conference on Software EngineeringShanghai,China.2006. ACM.
  3. Coyle Sharon, Conboy Kieran. Centre for Innovation and Structural Change, J.E. Cairnes. A CASE STUDY OF RISK MANAGEMENT IN AGILE SYSTEMS DEVELOPMENT. 17th European Conference on Information Systems (Newell S, Whitley EA, Pouloudi N, Wareham J, Mathiassen L eds.), 2567-2578, Verona, Italy.
  4. Ville Ylimannela Tampere. A MODEL FOR RISK MANAGEMENT IN AGILE SOFTWARE DEVELOPMENT
  5. Mauricio Concha, Marcello Visconti, and HernanAstudillo. Agile Commitments: Enhancing Business Risk Management in Agile Development Projects. 8th International Conference,XP 2007.
  6. Mikael Lindvall, Vic Basili, Barry Boehm, Patricia Costa , Kathleen Dangle, Forrest Shull, Roseanne Tesoriero, Laurie Williams, and Marvin Zelkowitz. Empirical Findings in Agile Methods. Second XP Universe and first Agile Universe Conference Chicago, 2002.
  7. Steffen Bartsch TZI. Practitioners' Perspectives on Security in Agile Development.
  8. Ahmed Sidky.James Arthur.Shawn Bohner (May 2007). A disciplined approach to adopting agile practices: the agile adoption framework.Innovations in Systems and Software Engineering 2007.
  9. A. Qumer, B. Henderson-Sellers. A framework to support the evaluation, adoption and improvement of agile methods in practice. (Nov 2008). Journal of Systems and Software Volume 81, Issu 11. Page 1899-1919. https://doi.org/10.1016/j.jss.2007.12.806
  10. Frank K.Y. Chan, James Y.L. Thong (2009) Acceptance of agile methodologies: A critical review and conceptual framework.
  11. Balasubramaniam Ramesh,* Lan Cao† & Richard Baskerville. Agile requirements engineering practices and challenges: an empirical study.
  12. JaanaNyfjord and Mira Kajko-Mattsson. Commonalities in Risk Management and Agile Process Models. International Conference of Software Engineering Advances, 2007. ICSEA 2007. IEEE.
  13. Barry Boehm University of Southern California. Get Ready for Agile Methods, with Care. Computer ( Volume: 35, Issue: 1, Jan 2002 ) IEEE.
  14. Barry Boehm, Richard Turner. Management Challenges to Implementing Agile Processes in Traditional Development Organizations. IEEE Software ( Volume: 22, Issue: 5, Sept.- Oct. 2005 )
  15. Emam Hossain, Muhammad Ali Babar, Hye-young Paik , June Verner. Risk Identification and Mitigation Processes for Using Scrum in Global Software Development: A Conceptual Framework. 2009 16th Asia-Pacific Software Engineering Conference.
  16. Tsun Chow, Dac-Buu Cao. A survey study of critical success factors in agile software projects. The Journal of Systems and Software 81 (2008) 961-971. https://doi.org/10.1016/j.jss.2007.08.020
  17. Christof Ebert, Bvs Krishna Murthy,Namo Narayan Jha. Managing Risks in Global Software Engineering: Principles and Practices. 2008 IEEE International Conference on Global Software Engineering.
  18. Susan Parente. The Art of Agile Risk Management. PM World Journal Vol. III, Issue VII - July 2014
  19. Tore Dyba˚ *, TorgeirDingsoyr. Empirical studies of agile software development: A systematic review. Information and Software Technology 50 (2008) 833-859. https://doi.org/10.1016/j.infsof.2008.01.006
  20. JaanaNyfjord. TOWARDS INTEGRATING AGILE DEVELOPMENT AND RISK MANAGEMENT (2008).
  21. Software Engineering Standards Committee of the IEEE Computer Society IEEE-SA Standards Board IEEE Standard for Software Life Cycle Processes-Risk Management (Approved 17 March 2001).
  22. Tore Dyba˚ *, Torgeir Dingsoyr Empirical studies of agile software development: A systematic review (24 January 2008).