Scrumbanfall: An Agile Integration of Scrum and Kanban with Waterfall in Software Engineering

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.

Work Standardization in IT Project Management Using Agile Methodologies.

“…In first approach case study solved with waterfall approach which consist of 5 stages (Figure 1). Engineering and Operations Management Warangal, Telangana, India, August 16-18, 2022 © IEOM Society International Figure 1.Waterfall Model 1.Requirements -This is the gathering of all customer requirements before the start of the project that enables the planning of each following phase (Bhavsar et al, 2020) 2.Design -This includes logical design and physical design: brainstorming solutions and turning them into specifications 3.Implementation -When developers take all requirements and specifications and write the code for them 4.Verification -Releasing the product/solution to the customer so they can review it and make sure it meets the requirements.…”

Evaluasi Metodologi CI/CD untuk Pengembangan Perangkat Lunak dalam Perkuliahan

“…Dalam metodologi pengembangan RPL tradisional, seperti misalnya: waterfall [19], Rapid Application Development (RAD) [20], dan sejenisnya; terdapat pembagian proses yang terkesan kaku mulai dari tahap perencanaan (analisis), organisasi (implementasi), aksi (instalasi), dan kontrol (evaluasi). Setiap tahap harus dinyatakan tuntas, barulah kemudian dapat dilakukan perpindahan ke tahap selanjutnya atau melakukan iterasi di tahap yang sama.…”

Point of Sale Framework-Based Code Igniter and Model View Controller Using Lighthouse Testing

“…ANKURKAR, 2015), As result of this research we can find out the development was standardized and non-business logic relationships automatically processed, there was much scalability so this gives us more efficiency through the implementations (Thakir Mahmood et al, 2019), In this study we aim to identify the elements that impact on agility in developing software products, in a gradual approach, from the traditional waterfall model towards approaches like Scrumban. Additionally, we will understand the social dimension of using agile methodologies in software development (STOICA et al, 2016), 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 (Bhavsar et al, 2020), The making of this POS application starts from the collecting all the data needed using observation and interview methods, designing an application models with an object-based approach diagram with application design tools in the form of a flowchart and Unified Modeling Language (UML) until the implementation of this POS application. With the application of the point of sales (POS) application can help the tasks of all stakeholders or related parties directly related to the POS application (Kambivi et al, 2020), The result of the evaluation was ranked with Functional Suitability as the highest.…”