Studi Komparasi Kerangka Kerja Manajemen Risiko dalam Scrum
DOI:
https://doi.org/10.32493/informatika.v7i2.17468Keywords:
Comparative Study, Framework, Risk Management, Software Engineering Project, ScrumAbstract
Risk management in software engineering projects describes an integrated design with methods, processes, and artifacts that continuously identify, analyze, control, and monitor risks, to prevent the project from failing. Agile methodology is an alternative to the traditional sequential software development process. Scrum is the most frequently used method based on the 2016 Agile development survey results. In recent years, there have been many studies that have produced a risk management framework for Scrum. However, risk analysis and the selection of responses to risks become a burden for stakeholders, so a framework is needed that can become a support system to help make decisions. This paper uses a comparative study of risk management framework literature and literature that utilizes tools for risk management. The research resulted in a new framework that integrates datasets and machine learning into a risk management framework, so further work can be done to test the effectiveness of the new frameworkReferences
Aslam, A., Ahmad, N., Saba, T., Almazyad, A. S., Rehman, A., Anjum, A., & Khan, A. (2017). Decision Support System for Risk Assessment and Management Strategies in Distributed Software Development. IEEE Access, 5, 20349–20373. https://doi.org/10.1109/ACCESS.2017.2757605
Chaouch, S., Mejri, A., & Ghannouchi, S. A. (2019). A framework for risk management in Scrum development process. Procedia Computer Science, 164, 187–192. https://doi.org/10.1016/j.procs.2019.12.171
Dey, P. K., Kinch, J., & Ogunlana, S. O. (2007). Managing risk in software development projects: a case study. Industrial Management & Data Systems.
Filippetto, A. S., Lima, R., & Barbosa, J. L. V. (2021). A risk prediction model for software project management based on similarity analysis of context histories. Information and Software Technology, 131. https://doi.org/10.1016/j.infsof.2020.106497
GarcÃa, Y. M., Muñoz, M., MejÃa, J., Gasca, G. P., & Mireles, A. (2018). Application of a risk management tool focused on helping to small and medium enterprises implementing the best practices in software development projects. Advances IGarcÃa, Y. M., Muñoz, M., MejÃa, J., Gasca, G. P., & Mireles, A. (2018). Application of a Risk Management Tool Focused on Helping to Small and Medium Enterprises Implementing the Best Practices in Software Development Projects. Advances in Intel, 746, 429–440. https://doi.org/10.1007/978-3-319-77712-2_41
Hammad, M., & Inayat, I. (2019). Integrating risk management in scrum framework. Proceedings - 2018 International Conference on Frontiers of Information Technology, FIT 2018, 158–163. https://doi.org/10.1109/FIT.2018.00035
Hammad, M., Inayat, I., & Zahid, M. (2019). Risk management in agile software development: A survey. Proceedings - 2019 International Conference on Frontiers of Information Technology, FIT 2019, 162–166. https://doi.org/10.1109/FIT47737.2019.00039
Jutte, B. (2012). Project Risk Management Handbook: the invaluable guide for managing project risks. Xlibris Corporation.
Kurniawan, J. (2020). Kelola Risiko dengan Scrum Pillar: Transparansi, Inspeksi, dan Adaptasi. In bumntrack.co.id (p. 1).
Moran, A. (2014). Agile risk management. In Agile Risk Management (pp. 33–60). Springer.
Nyfjord, J. (2008). Towards integrating agile development and risk management.
Pandian, C. R. (2006). Applied software risk management: A guide for software project managers. Auerbach Publications.
Puri, A., & Sharma, S. (2020). Risk Management in Software Engineering Using Big Data. Proceedings of International Conference on Intelligent Engineering and Management, ICIEM 2020, 63–68. https://doi.org/10.1109/ICIEM48762.2020.9160170
Rudy, T. (2016). Manajemen Proyek Sistem Informasi, bagaimana mengolah proyek sistem informasi secara efektif & efisien. Andi Offset: Yogyakarta.
Schwaber Ken, & Sutherland Jeff. (2020). Panduan Definitif untuk Scrum: Aturan Permainan. Scrum.Org, November, 1–17.
Downloads
Published
Issue
Section
License
Authors who publish with this journal agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access).
Jurnal Informatika Universitas Pamulang have CC-BY-NC or an equivalent license as the optimal license for the publication, distribution, use, and reuse of scholarly work.
In developing strategy and setting priorities, Jurnal Informatika Universitas Pamulang recognize that free access is better than priced access, libre access is better than free access, and libre under CC-BY-NC or the equivalent is better than libre under more restrictive open licenses. We should achieve what we can when we can. We should not delay achieving free in order to achieve libre, and we should not stop with free when we can achieve libre.
Jurnal Informatika Universitas Pamulang is licensed under a Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)
YOU ARE FREE TO:
- Share : copy and redistribute the material in any medium or format
- Adapt : remix, transform, and build upon the material for any purpose, even commercially.
- The licensor cannot revoke these freedoms as long as you follow the license terms