ScrumFall: A Hybrid Software Process Model

Full Text (PDF, 479KB), PP.41-48

Views: 0 Downloads: 0


Md Shamsur Rahim 1,* AZM Ehtesham Chowdhury 1 Dip Nandi 1 Mashiour Rahman 1 Shahadatul Hakim 2

1. American International University-Bangladesh/Computer Science, Dhaka, 1229, Bangladesh

2. Enosis Solutions, Dhaka, 1212, Bangladesh

* Corresponding author.


Received: 4 Aug. 2018 / Revised: 16 Sep. 2018 / Accepted: 22 Sep. 2018 / Published: 8 Dec. 2018

Index Terms

Agile, Hybrid Process Model, Software Development Life Cycle, Software Process Model


Every software project is unique in its own way. As a consequence, a single software process model cannot be suitable for all types of projects. In the real world, practitioners face different difficulties with the existing process models during development. Still, they cope up with the challenges by tailoring the software development lifecycle according to their needs. Most of these custom-tailored practices are kept inside the walls of the organizations. However, sharing these proven and tested practices as well as acquired knowledge and experience would be highly beneficial for other practitioners as well as researchers. So in this paper, we have presented a software process model which contains the characteristics of both Scrum and Waterfall model and named it “ScrumFall”. This model has been practicing in an Anonymous Software Development Company, Bangladesh to solve the shortcomings of Scrum and Waterfall models. Moreover, we have analyzed the performance and suitability for applying this process model. The result shows that this process model is highly effective for the certain projects.

Cite This Paper

Shamsur Rahim, AZM Ehtesham Chowdhury, Dip Nandi, Mashiour Rahman, Shahadatul Hakim, "ScrumFall: A Hybrid Software Process Model", International Journal of Information Technology and Computer Science(IJITCS), Vol.10, No.12, pp.41-48, 2018. DOI:10.5815/ijitcs.2018.12.06


[1]G. Elliott, Global Business Information Technology. Pearson Education UK, 2004, p. 87.
[2]K. Petersen and C. Wohlin, "The effect of moving from a plan-driven to an incremental software development approach with agile practices", Empirical Software Engineering, vol. 15, no. 6, pp. 654-693, 2010.
[3]R. Pressman, Software engineering: a practitioner's approach. Palgrave Macmillan, 2005, pp. 39-40.
[4]M.S. Rahim, A E. Chowdhury, D. Nandi, and M. Rahman, “Issue Starvation in Software Development: A Case Study on the Redmine Issue Tracking System Dataset,” Journal of Telecommunication, Electronic and Computer Engineering, vol. 9, no. 3, pp. 185–189, Oct. 2017.
[5]A. E. Chowdhury, A. Bhowmik, H. Hasan, and M. S. Rahim, “Analysis of the veracities of industry used software development life cycle methodologies,” arXiv preprint arXiv:1805.08631 [cs], May. 2018.
[6]M.S. Rahim, M. Hasan, A.E. Chowdhury and S. Das, “Software engineering practices and challenges in Bangladesh: A preliminary survey,” Journal of Telecommunication, Electronic and Computer Engineering, vol. 9, no. 3, pp. 163–169, Oct. 2017.
[7]S. Conte, H. Dunsmore and V. Shen, Software engineering metrics and models. Menlo Park, Calif.: Benjamin/Cummings, 1991.
[8]R. Pressman, Software engineering: a practitioner's approach. Palgrave Macmillan, 2005, pp. 41-42.
[9]C. Larman and V. Basili, "Iterative and incremental developments. a brief history", Computer, vol. 36, no. 6, pp. 47-56, 2003.
[10]B. Boehm and W. Hansen, "Spiral Development: Experience, Principles, and Refinements", Carnegie Mellon University, Pittsburgh, 2000.
[11]M. Smith, Software prototyping. London: McGraw-Hill, 1991.
[12]]N. Ruparelia, "Software development lifecycle models", ACM SIGSOFT Software Engineering Notes, vol. 35, no. 3, p. 8, 2010.
[13]R. Martin, Agile software development: principles, patterns, and practices, 1st ed. United States of America: Prentice Hall, 2002.
[14]K. Schwaber and J. Sutherland, The scrum guide. Scrum Alliance. Scrum Alliance, 2011.
[15]K. Beck and C. Andres, Extreme programming explained: embrace change. Addison-Wesley. Reading, 1999.
[16]N. K. Alexandros, D. P. Sakas, D. S. Vlachos, and N. K. Dimitrios, “Comparing Scrum and XP Agile Methodologies Using Dynamic Simulation Modeling,” Strategic Innovative Marketing Springer Proceedings in Business and Economics, pp. 391–397, 2017.
[17]L. Plonka, H. Sharp, P. Gregory and K. Taylor, "UX design in agile: a DSDM case study", in International Conference on Agile Software Development, 2014.
[18]S. Palmer and J. Felsing, A practical guide to feature-driven development. Upper Saddle River, New Jersey: Prentice Hall PTR, 2002.
[19]D. West, M. Gilpin, T. Grant, and A. Anderson, “Forrester,” Forrester, 26-Jul-2011. [Online]. Available: Is The Reality Of Agile For Most Organizations Today/-/E-RES60109#. [Accessed: 22-Jul-2018].
[20]S. Nerur, R. Mahapatra and G. Mangalaraj, "Challenges of migrating to agile methodologies", Communications of the ACM, vol. 48, no. 5, pp. 72-78, 2005.
[21]R. Chopra, Software quality assurance: a self-teaching introduction. Dulles, VA: Mercury Learning and Information, 2018.
[22]R. Hoda, J. Noble and S. Marshall, "Self-Organizing Roles on Agile Software Development Teams", IEEE Transactions on Software Engineering, vol. 39, no. 3, pp. 422-444, 2013.