International Journal of Innovative Technology and Exploring Engineering (IJITEE) ISSN: 2278-3075, Volume-9 Issue-4, February 2020 2075 Published By: Blue Eyes Intelligence Engineering & Sciences Publication Retrieval Number: D1437029420/2020©BEIESP DOI: 10.35940/ijitee.D1437.029420 Abstract: Software industries have been growing with the rise of automation technologies and looking for change in their software development practices to gain the benefits of automation technologies for achieving their business goals. Agile Business Process Reengineering (ABPR) is trending approach for Software Engineering Management (SEM) in software industries, which helps software development organization in transformation of software development practices. Scrum and Kanban are fascinating Agile methodologies adopted by Software Engineering Management practitioners. Scrumban, a mixture of both Scrum and Kanban, has derived strengths of both frameworks, in formation of a robust framework against challenges of Agile Software Engineering (ASE) methodologies like work flow control, lead time management, product delivery that could not be solved by Scrum or Kanban as a standalone framework. But still some of challenges, which are out of scope of Scrumban like project requirement documentation, planning, scheduling, estimation and clear product vision at initial stage of the project. Such issues have raised a request of research for Software Process Reengineering (SPR) in Scrumban by customizing its structure for to form the next level of hybrid framework. The Traditional SDLC methodology ‘Waterfall’ has answers for such issues. An empirical analysis, for resolution of such issues, with the help of ‘Waterfall’ model and its life cycle protocols is the main goal this research study by integrating Scrum and Kanban with Waterfall to form a hybrid framework ‘Scrumbanfall’ aligning Kanban in center of integration under the boundary of Scrum rules. This research also highlights limitations of Scrumbanfall like team members and their roles and capabilities for the large scaled project having team members in distributed environment, which open the door for next level of research to overcome such challenges using further hybridization of Scrumbanfall. Keywords: Scrum, Kanban, Scrumban, Scrum Challenges, AM - Agile Methodology, ABPR – Agile Business Process Reengineering, BPR - Business Process Reengineering, ESE – Empirical Software Engineering, SPR – Software Process Reengineering, SEM – Software Engineering Management, SE – Software Engineering Revised Manuscript Received on February 04, 2020. 1 Correspondence Author Krunal Bhavsar, Research Scholar, Computer Science & Engineering, Indus University, Ahmedabad, India. Email: krunalbhavsar@engineer.com ; krunalbhavsar.rs@indusuni.ac.in . Contact: +91-9737007007. Dr. Vrutik Shah, Research Guide, Computer Science & Engineering, Indus University, Ahmedabad, India. Dr. Samir Gopalan, Research Co-Guide, Business Administration & Management, Indus University, Ahmedabad, India. I. INTRODUCTION Scrumbanfall is the agile hybridization of Scrum and Kanban with Waterfall in Software Engineering Management (SEM). Agile is the roof for the software development practices, built on the principles of Agile Manifesto [8] and a range of methods have been evolved as a standard SEM practices. Agile changes the way of thinking about product vision as it follows outside-in process flow as a reinvention approach, in terms of customer value, product quality, productivity maximization and roles in the team of software product development [11] . Out of all, Scrum and Kanban covers and achieves all of these core values for the software development organization. Scrum and Kanban both are agile based frameworks and derive characteristics of Agile Manifesto [8] principles as base concept. Scrum is very popular [4] Agile Software Engineering Management (ASEM) framework amongst all Agile Methodologies (AM); due to its characteristics like artifacts, events, pillars, roles and values, which has transformed software practices in software development organizations by enabling organizations capabilities towards Agile Business Process Reengineering (ABPR). Scrum is a first generation method and primary choice, while Kanban is the second generation method and secondary choice amongst the Agile family and both are extensively used in software development organizations. All essential factors should be considered while selecting framework as a standard practices for the software development and management approach. Scrum is facing some challenges [12] with software development practices like lead time management and work flow control, direct involvement of external stakeholders as a critical decision maker, team size and their role specific capabilities for large scaled software product development in distributed environment, complete estimation of product and unclear vision of product at initial stage of project. Scrumban [18] can overcome few challenges like work flow control, lead time management; continuous integration and delivery of software product. Yet Scrumban can’t cover all the challenges of software project development. The proposed Scrumbanfall will help in resolving some of the issues like project requirement documentation, planning, scheduling, estimation and clear product vision at initial stage of the product. Scrumbanfall: An Agile Integration of Scrum and Kanban with Waterfall in Software Engineering Krunal Bhavsar, Vrutik Shah, Samir Gopalan