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

2020 ◽  
Vol 9 (4) ◽  
pp. 1626-1634
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Engineering Management ◽  
Organizational Capabilities ◽  
Software Project ◽  
Project Development ◽  
Development Organizations ◽  
Internal States ◽  
Development Processes ◽  
Development And Management

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.

scholarly journals Scrum Challenges: An Agile Process Reengineering in Software Engineering

2020 ◽  
Vol 9 (4) ◽  
pp. 1233-1241
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Research Work ◽  
Engineering Management ◽  
Good Time ◽  
Process Reengineering ◽  
Successful Implementation ◽  
Software Project ◽  
Hybrid Form ◽  
Development Organizations

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.

scholarly journals Business Process Reengineering: A Scope of Automation in Software Project Management using Artificial Intelligence

2019 ◽  
Vol 9 (2) ◽  
pp. 3589-3594
Keyword(s):  
Artificial Intelligence ◽  
Project Management ◽  
Software Engineering ◽  
Software Development ◽  
Analytical Study ◽  
Software Project ◽  
Software Project Management ◽  
Development Organization ◽  
Development Organizations ◽  
Management Procedures

This research paper aims an analytical study on the software development organization insight into trending automation technologies and their implementation Software Engineering Management (SEM) processes. Software Project Management (SPM) is a scientific art for planning, controlling execution and monitoring. SPM approaches are more focusing towards the essential requirement for the success of software project development. It has been very challenging to manage software development using existing project management procedures driven by software development organizations and this is one of the areas of problem statement for this research. This paper discusses an analytical study for the requirements and consideration of BPR in SPM, explores to spot and emphasizes the important success factors for the execution of a BPR using benefits of Artificial Intelligence (AI) in software development organization. BPR is organizational mechanism that improves ability to respond to challenges of qualitative result by change and improvement in software engineering processes, productivity, product quality and competitive advantages. AI will be the best approach and scope of automation SEM processes for software development organizations. This paper also represents a conceptual view of software engineering model shift for improvements in capability of project managers to handle agile thinking and problem solving for betterment of SPM using Artificial Intelligence.

scholarly journals Using git metrics to measure students' and teams' code contributions in software development projects

2021 ◽  
Vol 24 (2) ◽  
Author(s):  
Sivana Hamer ◽  
Christian Quesada-López ◽  
Alexandra Martínez ◽  
Marcelo Jenkins
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Source Code ◽  
Version Control ◽  
Individual Student ◽  
Development Projects ◽  
Project Development ◽  
Inequality Measures ◽  
Software Artifacts ◽  
Development Processes

Many software engineering courses are centered around team-based project development. Analyzing the source code contributions during the projects’ development could provide both instructors and students with constant feedback to identify common trends and behaviors that can be improved during the courses. Evaluating course projects is a challenge due to the difficulty of measuring individual student contributions versus team contributions during the development. The adoption of distributed version control sys-tems like git enable the measurement of students’ and teams’ contributions to the project.In this work, we analyze the contributions within eight software development projects,with 150 students in total, from undergraduate courses that used project-based learning.We generate visualizations of aggregated git metrics using inequality measures and the contribution per module, which offer insights into the practices and processes followed by students and teams throughout the project development. This approach allowed us to identify inequality among students’ contributions, the modules where students con-tributed, development processes with a non-steady pace, and integration practices render-ing a useful feedback tool for instructors and students during the project’s development.Further studies can be conducted to assess the quality, complexity, and ownership of the contributions by analyzing software artifacts. 

scholarly journals Scrum: An Agile Process Reengineering in Software Engineering

2020 ◽  
Vol 9 (3) ◽  
pp. 840-848 ◽  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Control Theory ◽  
Engineering Management ◽  
Vital Role ◽  
Team Members ◽  
Software Products ◽  
Development Organizations ◽  
Organizational Mechanism ◽  
Agile Process

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.

Multiagent System for Supporting the Knowledge Management in the Software Process

2011 ◽  
pp. 96-113 ◽  
Author(s):  
Francisco Milton Mendes Neto ◽  
Marçal José de Oliveira Morais
Keyword(s):  
Knowledge Management ◽  
Software Engineering ◽  
Software Development ◽  
Intelligent Agents ◽  
Multiagent System ◽  
Software Process ◽  
Development Organizations ◽  
Wide Range ◽  
Development Processes ◽  
Knowledge Intensive

The software process consists of knowledge-intensive procedures, involving various profiles, which handle a wide range of information. The adoption of a solution that satisfies the knowledge demands related to software engineering is not a trivial task. Despite all the investment made by research institutions and software development organizations in automated environments to support the software process, the quality levels and the productivity rates they need has not been reached. In software engineering, the experience, which helps avoid mistakes of the past and improve decision making, still lies mainly in the organization collaborators. This chapter intends to contribute to software engineering by proposing a new approach to support the capture, packaging, storage, mapping, maintenance and retrieval of the knowledge related to the software process. The approach will support the software process through the creation of a knowledge management model to assist the development of intelligent agents that can (i) realize the knowledge needs, (ii) interact with the Information Systems and (iii) support executing the software developers’ tasks. In other words, the chapter proposes creating a multiagent system to manage knowledge related to the execution of software development processes. This system will be the result of implementing the knowledge management models for supporting software process that will also be proposed in this chapter. It will consist of an Information System integrated with a knowledge base related to the implementation of software development processes.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Boosting the Competitiveness of Organizations With the Use of Software Engineering

2021 ◽  
pp. 198-216
Author(s):  
Mirna Muñoz
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Development Process ◽  
Research Work ◽  
Software Development Process ◽  
The Core ◽  
Development Organizations ◽  
Technological Base ◽  
The One

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.

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

2020 ◽  
Vol 9 (4) ◽  
pp. 2075-2084
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Time Management ◽  
Engineering Management ◽  
Process Reengineering ◽  
Team Members ◽  
Development Organization ◽  
Business Goals ◽  
Hybrid Framework ◽  
Software Development Practices

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.

Sign in / Sign up

Export Citation Format

Share Document