Machine Learning: A Software Process Reengineering in Software Development Organization

Business Process Reengineering (BPR) is an organizational strategy seeking identification of critical factors affecting software development practices in Software Engineering Management (SEM). The agile approaches opened the door of BPR in software development organizations. Dynamically changing technological environment has invited software development organizations, towards adoption of reengineering of strategies and practices. Nowadays, Scrum has been trending as an agile framework for Software Engineering Management (SEM) in software development organizations but considerable research work has not been done with Scrum and its successful implementation yet. The goal of this research is to highlight weaknesses and limitations of Scrum like project level documentation, planning, estimation, progress tracker, CICD etc.; and identification of challenges and issues with implementation of Scrum in software project development like large scaled project in distributed work environment with multiple Scrum teams, organizational structure, lack of knowledge ad awareness about Scrum; using empirical analysis and literature studies. The result of this research will open the door for the next stage of research to overcome the limitation and issues with implementation of Scrum and raise a request of BPR towards focus on improvement in SEM practices in software development organizations by proposing proper training about the empiricism control theory of Scrum that helps organizations in understanding the successful implementation of Scrum and its benefits. This research also raises a question in the form of suggestion that it is good time for a hybrid form of Scrum with other standard agile based frameworks or traditional SDLC methodologies.

Section: Scrum and Bprmentioning

confidence: 99%

Section: Future Enhancementmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Scrum Challenges: An Agile Process Reengineering in Software Engineering

Bhavsar*,

Shah,

Gopalan

2020

“…Process Life Cycle Framework (PLCF) [29] is a structural way for imitating agile transformation in software development practices. Along with this, technologies are emerging in the software development industries with the evolution of AI (Artificial Intelligence) [17] , [45] and ML (Machine Learning) [22] technologies. Hence their contribution to Software Engineering Management should be considerable with the ABPR by software development organizations.…”

Section: Introductionmentioning

confidence: 99%

Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

Bhavsar*¹,

Shah²,

Gopalan³

2020

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.

“…Estimation of software development ensures cost (budget) and time limitation for building quality software [34] along with specification of functional and non-functional requirement of the project [35] . ABPR needs proper PLCF (Process Life Cycle Framework) [24] suitable to organizational structure using power of automation technologies like AI (Artificial Intelligence) [29] and ML (Machine Learning) [36] for Software Project Management (SPM) frameworks in software development organizations as the emergence of such automation technologies have capabilities to automate the project tasks and business operations as per organizational requirement [37] .…”

Section: Introductionmentioning

confidence: 99%

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

Bhavsar*¹,

Shah²,

Gopalan³

2020

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.