BPR (Business Process Re-engineering) is an organizational mechanism leading organization towards change management as and when it is required. In the form BPR, Agile practices have had a remarkable impact on Software Engineering Management (SEM) in software development organizations across the world. It has enhanced collaboration and productivity of Software Engineering (SE) teams and improved the level of quality of software products. Nowadays Scrum has been trending into software development organizations as a standard SDLC approach. Scrum is the framework of the Agile methodology, built on empiricism control theory, asserts that experience brings knowledge and increases decision making capabilities. The empiricism control theory is built on three pillars: Adaptation, Inspection and Transparency. This research study presents Scrum as a trending SDLC framework using empirical analysis. We have analyzed literature reviews, case studies, and research surveys; and implemented Scrum in our software development unit and carried out the reasons, why Scrum is trending in software development organizations. How the scrum artifacts, events and values play a vital role in upholding the Scrum pillars and strengthen the capabilities of Scrum team members to address the software engineering management challenges; compared to traditional software development approaches.

Software Engineering (SE) technologies are emerging day by day and seeking ABPR (Agile Business Process Reengineering) for Software Engineering Management (SEM) frameworks in software development organizations. BPR can enable organizational capabilities to initiate and implement critical change in execution. Under the roof of agile and on the base of empiricism, the Scrum has been proven itself as an ABPR approach for software engineering management in the software development organizations, across the world, by improving productivity, self-organization and collaboration for standard software development processes. Scrum has been leading software project development practices using its own characteristics: Artifacts, Pillars, Values, Events and Roles. But still software project development organizations are facing some issues with their software project development and management processes, like no documentation policy which results into inaccurate estimation, internal states of each work item flowing through the Scrum Board, Sprint tracker and prediction towards goal achievement which can be considered as challenges for Scrum due its limitations as well as Scrum does not allow, any alteration in its rules. Such issues have raised a question against implementation of Scrum and have opened the door for the next level of research to answer the question, how to overcome the limitations of Scrum. Kanban can provide the solution to some of these issues but it can’t provide complete SEM solutions to software Development Organizations. The aim of this research study is empirical analysis about how the formation of hybrid framework Scrumban as an integration of Scrum with Kanban, can resolve challenges of Scrum; using literature reviews, case study reviews, and research surveys; and this research has proposed a conceptual customized Scrumban framework, by keeping Kanban in the center of customization under the bound of Scrum rules. This research also concludes limitations of Scrumban, like project documentation, planning, large scaled project, distributed environment, team capabilities etc.; as each method has its own limitations.

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.