EXPLORING CHALLENGES, BENEFITS AND GOOD PRACTICES RELATED TO SCRUMBAN SOFTWARE DEVELOPMENT METHODOLOGY
DOI:
https://doi.org/10.24867/22OI02GajicKeywords:
Scrumban, Agile methodologies, Scrum, KanbanAbstract
This paper presents an analysis of Scrumban methodology for software development within the information technology industry. In order to analyze Scrumban model in more detail, the systematic literature review has been conducted. Based on the results of systematic literature review, the benefits, challenges and good practices related to Scrum and Kanban agile methodologies were analyzed, because those methodologies combined represent Scrumban hybrid model. Тhis paper also presents the way of integrating Scrumban hybrid model into Adobe’s operations.
References
[1] O. Hazzan and Y. Dubinsky, “The Agile Manifesto,” SpringerBriefs Comput. Sci., vol. 0, no. 9783319101569, pp. 9–14, 2014, doi: 10.1007/978-3-319-10157-6_3.
[2] R. E. Quelal, M. Villavicencio, and L. E. Mendoza, “A Survey of Agile Software Development Methodologies in Ecuador.”
[3] R. Aurisch, M. Ahmed, and A. Barkat, “An outlook at Agile methodologies for the independent games developer,” Int. J. Comput. Appl., vol. 43, no. 8, pp. 812–818, 2021, doi: 10.1080/1206212X.2019.1621463.
[4] W. Zayat and O. Senvar, “Framework Study for Agile Software Development Via Scrum and Kanban,” International Journal of Innovation and Technology Management, vol. 17, no. 4. World Scientific, Jun. 01, 2020, doi: 10.1142/S0219877020300025.
[5] “How detailed should tasks within a user story be for agile teams?” https://techbeacon.com/app-dev-testing/how-detailed-should-tasks-within-user-story-be-agile-teams (pristupljeno Sep. 20, 2022).
[6] B. Kitchenham, - “Procedures for Performing Systematic Reviews”, 2004.
[7] E. Weflen, C. A. MacKenzie, and I. V. Rivero, “An influence diagram approach to automating lead time estimation in Agile Kanban project management,” Expert Syst. Appl., vol. 187, Jan. 2022, doi: 10.1016/j.eswa.2021.115866.
[8] P. Clarke, R. V. O’Connor, and M. Yilmaz, “In search of the origins and enduring impact of agile software development,” in ACM International Conference Proceeding Series, May 2018, pp. 142–146, doi: 10.1145/3202710.3203162.
[9] J. Filipe, A. Ghosh, R. O. Prates, and L. Zhou, “Communications in Computer and Information Science 1388 Editorial Board Members.” [Online]. Available: http://www.springer.com/series/7899.
[2] R. E. Quelal, M. Villavicencio, and L. E. Mendoza, “A Survey of Agile Software Development Methodologies in Ecuador.”
[3] R. Aurisch, M. Ahmed, and A. Barkat, “An outlook at Agile methodologies for the independent games developer,” Int. J. Comput. Appl., vol. 43, no. 8, pp. 812–818, 2021, doi: 10.1080/1206212X.2019.1621463.
[4] W. Zayat and O. Senvar, “Framework Study for Agile Software Development Via Scrum and Kanban,” International Journal of Innovation and Technology Management, vol. 17, no. 4. World Scientific, Jun. 01, 2020, doi: 10.1142/S0219877020300025.
[5] “How detailed should tasks within a user story be for agile teams?” https://techbeacon.com/app-dev-testing/how-detailed-should-tasks-within-user-story-be-agile-teams (pristupljeno Sep. 20, 2022).
[6] B. Kitchenham, - “Procedures for Performing Systematic Reviews”, 2004.
[7] E. Weflen, C. A. MacKenzie, and I. V. Rivero, “An influence diagram approach to automating lead time estimation in Agile Kanban project management,” Expert Syst. Appl., vol. 187, Jan. 2022, doi: 10.1016/j.eswa.2021.115866.
[8] P. Clarke, R. V. O’Connor, and M. Yilmaz, “In search of the origins and enduring impact of agile software development,” in ACM International Conference Proceeding Series, May 2018, pp. 142–146, doi: 10.1145/3202710.3203162.
[9] J. Filipe, A. Ghosh, R. O. Prates, and L. Zhou, “Communications in Computer and Information Science 1388 Editorial Board Members.” [Online]. Available: http://www.springer.com/series/7899.
Downloads
Published
2023-05-09
Issue
Section
Information Systems Engineering
