A Scrumban Integrated Approach to Improve Software Development Process and Product Delivery

Authors

  • Sai Nikhil Donthi Department of Software Engineering, University of Houston Clear Lake, LTIMindtree, Client – Oil and Gas Industry Houston, Texas , USA

Keywords:

Scrum, Kanban, Scrumban, productivity, sprint, LSD, SDLC, flexibility

Abstract

Scrum and Kanban have been the two traditional Agile practices which has been depicted as successful in enhancing software development processes, while each has its own drawbacks when implemented in software IT industry and put into practice individually. Scrum enforces sprint, roles, ceremonies, and load calculation which can occasionally result in overhead and rigidity. Although Kanban is flexible and having constant flow, it might not include task batching or structured prioritization. The research challenge of optimising the productivity of the software development lifecycle by integrating both of these strategies into a hybrid framework called the Scrumban. Methodologically, it synthesizes findings from industry case studies, scholarly literature, and real-world implementation addressing workflow visualization, work-in-progress (WIP) limits, sprint process and team role definitions. The study explores how Scrumban mitigates the drawbacks of its earlier models with increasing productivity, resource use, and deliver quality. Scrumban will serve as a hybrid framework to enhance the entire software development lifecycle, as evidenced by real-world use cases and KPIs such as execution time and defect reduction. Significant findings indicate that Scrum ban enhances adaptation in unpredictable circumstances, helps with continuous delivery, and supports cross-functional collaboration. Scrumban makes use of Kanban's flow productivity and Scrum's structured planning to minimize redundant work, fix bottlenecks, while enhancing transparency. Use cases from enterprise applications, promotional platforms, and incident reporting applications prove Scrumban’s scalability and savings potential. This research determines its findings that Scrum ban is suitable to organizations transitioning from traditional Agile approaches because it is a complete approach that supports both shifting business needs and developments in technology.

References

lqudah, M., & Razali, R. (2017). A comparison of scrum and Kanban for identifying their selection factors. 2017 IEEE International Conference on Environment and Electrical Engineering (EEEIC), 1–6. https://doi.org/10.1109/ICEEI.2017.8312434

Hema, Thota, S., Naresh Kumar, S., Padmaja, C., Rama Krishna, C. B., & Mahender, K. (2020). Scrum: An Effective Software Development Agile Tool. IOP Conference Series. Materials Science and Engineering, 981(2). https://doi.org/10.1088/1757- 899X/981/2/022060

Agh, & Ramsin, R. (2021). Scrum metaprocess: a process line approach for customizing Scrum. Software Quality Journal, 29(2), 337–379. https://doi.org/10.1007/s11219-021-09551-4

Al-Zewairi, Biltawi, M., Etaiwi, W., & Shaout, A. (2018). Agile Software Development Methodologies: Survey of Surveys. Estonian Journal of Earth Sciences, 67(3), 74–. https://doi.org/10.4236/jcc.2017.55007

Sultania. (2015). Developing software product and test automation software using Agile methodology. Proceedings of the 2015 Third International Conference on Computer, Communication, Control and Information Technology (C3IT), 1–4. https://doi.org/10.1109/C3IT.2015.7060120

Çetin, & Onay Durdu, P. (2019). Blended Scrum model for software development organizations. Journal of Software: Evolution and Process, 31(2), e2147–n/a. https://doi.org/10.1002/smr.2147

Žužek, Kušar, J., Rihar, L., & Berlec, T. (2020). Agile-Concurrent hybrid: A framework for concurrent product development using Scrum. Concurrent Engineering, Research and Applications, 28(4), 255–264. https://doi.org/10.1177/1063293X20958541

Adam Cetnerowski. (2015). The Scrumban [R] Evolution: Getting the Most Out of Agile, Serum, and Lean Kanban [Review of The Scrumban [R] Evolution: Getting the Most Out of Agile, Serum, and Lean Kanban]. Software Quality Professional, 18(1), 34–. American Society for Quality.

Schaefer, & Söllner, D. (2017). DevOps by Scrumban. HMD practice in business informatics, 54(2), 251–260. https://doi.org/10.1365/s40702-017-0301-x

Abdullah Albarq, & Qureshi, R. (2018). The Proposed L-Scrumban Methodology to Improve the Efficiency of Agile Software Development. International Journal of Information Engineering and Electronic Business, 10(3), 23–35. https://doi.org/10.5815/ijieeb.2018.03.04

STOICA, GHILIC-MICU, B., MIRCEA, M., & USCATU, C. (2016). Analyzing Agile Development – from Waterfall Style to Scrumban. Informatica Economica, 20(4/2016), 5–14. https://doi.org/10.12948/issn14531305/20.4.2016.0 1

Law, & Lárusdóttir, M. K. (2015). Whose Experience Do We Care About? Analysis of the Fitness of Scrum and Kanban to User Experience. International Journal of Human-Computer Interaction, 31(9), 584–602. https://doi.org/10.1080/10447318.2015.1065693

Lynn, R. (2021, October 13). Kanban system: Maximize time and improve efficiency. Planview. Retrieved November 21, 2021, from https://www.planview.com/resources/guide/introdu ction-to-kanban/kanban-system-maximize-time/

Patil, & Neve, J. R. (2018). Productivity Improvement of Software Development Process Through Scrumban: A Practitioner’s Approach. 2018 International Conference on Advances in Communication and Computing Technology (ICACCT), 314–318. https://doi.org/10.1109/ICACCT.2018.8529405

Downloads

Published

2025-09-26

How to Cite

Sai Nikhil Donthi. (2025). A Scrumban Integrated Approach to Improve Software Development Process and Product Delivery. Emerging Frontiers Library for The American Journal of Interdisciplinary Innovations and Research, 7(09), 70–82. Retrieved from https://emergingsociety.org/index.php/efltajiir/article/view/310