Agile Software Development Process Research Articles

Analysis of Traditional and Agile Software Development Process for Developing Recommender Model using Machine Learning

Objective: To create an AI-powered recommendation system that is designed for IT professionals to help them choose the best software development approaches. Through the use of specified data parameters. Methods: The recommendation system will make use of machine learning algorithms and data analysis methods to examine team dynamics, project needs, and other variables. The technology will enable developers to improve the quality of products and speed up the development process by recommending suitable development methodologies. Data parameters considered for the development of the recommendation model fall into four categories: requirements, user involvement, development team, type of project, and risk associated with it. Findings: Existing recommendation systems developed by different researchers are applicable for only requirement elicitation and to recommend different phases of the development process, whereas systems that will help select development methodology are not available in the existing systems. Among the five machine learning algorithms applied in the recommender system building process, the DecisionTree Classifier and RandomForest Classifier exhibit superior performance, achieving 100% accuracy, while the Kneighbors Classifier indicates 94.74% accuracy. Novelty: This study of systems introduces a novel approach to software development methodology, a recommender system, which helps IT developers select the best appropriate development approach for the development of a software product or project based on the type of project to be built and other data parameters. Keywords: Agile, Development, Requirements, Methodology, User, Customer

Modelling the enablers of productivity of enterprise-level Agile software development process using modified TISM approach

Purpose This study aims to examine the enablers of productivity of enterprise-level Agile development process using modified total interpretative structural modeling (TISM). The two main objectives of the current study are to determine the variables influencing enterprise-level agile development productivity and to develop modified TISM for the corresponding components. Design/methodology/approach To identify enablers of the productivity of enterprise-level agile software development process a literature review and opinions of domain experts were collected. A hierarchical relationship among variables that show direct and indirect influence is created using the modified TISM (M-TISM) technique with Cross Impact Matrix-Multiplication Applied to Classification analysis. This study examined and analyzed the relationships between the determinants within the enterprise using a M-TISM technique. Findings With the literature review, the study could identify ten enabling factors of the productivity of Agile development process at the enterprise level. Results depict that program increment (PI) planning and scalable backlog management, continuous integration and continuous delivery (CI/CD), agile release trains (ART), agile work culture, delivery excellence, lean and DevOps practices, value stream mapping (VMS), team skills and expertise, collaborative culture, agile coaching, customer engagement have an impact on the productivity of enterprise-level Agile development process. The results show that team collaboration, agile ways of working and customer engagement have a greater impact on productivity improvement for enterprise-level Agile development process. Research limitations/implications The developed model is useful for organizations employing scaled Agile development processes in software development. This study provides a recommended listing of key enablers, that may enable productivity improvements in the Agile development process at the enterprise level. Strategists should focus on team collaboration and Agile project management. This study offers a modified TISM model to academicians to help them understand the effects of numerous variables on maintaining the productivity of an enterprise-level Agile. The identified characteristics and their hierarchical structure can help project managers during the execution of Agile projects at the enterprise level, more effectively, increasing their success and productivity. Originality/value The study addresses the gap in the literature by interpretative relationships between the identified enabling factors. The model validation is carried out by a panel of nine experts from several information technology organizations deploying Agile software development at the enterprise level. This unique method broadens the knowledge base in Agile software development at scale and provides project managers and practitioners with a practical foundation.

Information Security Integration with Agile Software Development: Systematic Literature Review and Expert Judgement

Many businesses are using the Agile Software Development (ASD) to react to changing needs and provide functional values quickly. Information security, on the other hand, is seen as a non-functional requirement. In consequence, information security is frequently ranked lower than functional needs in ASD. The goal of this study is to present a unified perspective on how researchers integrate information security into agile software development. This study uses Systematic Literature Review (SLR) approach from ACM, IEEE, ScienceDirect, and Scopus. This study identified several key groups related to the integration of information security with ASD: agile methodologies, agile ceremonies, advantages, and issues. According to the findings of this study, all agile ceremonies contain some form of enhancement in process or artifacts linked to security. These findings have also been validated by expert judgment who have experience working in the project team that have integrated information security into agile software development process.

Critical Success Factors of Agile Software Development - A Systematic Literature Review

Agile software development has gained more popularity due to its capacity to manage constantly changing needs and generate high-quality software in less time. However, several success factors are required for an agile project to succeed. Agile development technique, delivery strategy, project team training, customer and staff involvement, management commitment, organizational culture, communication, and project management process are critical success factors (CSF) discovered in this study. This study's goal is to locate and evaluate these crucial elements of the agile software development methodology's success. A systematic literature review was conducted to study and analyze the previous studies to identify the CSFs in agile development. The findings of the literature review indicate that technical, people, organizational, and process factors are crucial for the success of agile projects. Each CSF falls into any one of these factors. Overall, this study's findings emphasize the significance of CSFs in the agile software development process. Organizations and software development teams can enhance their agile processes and raise the likelihood of project success by being aware of these aspects. Teams may create high-quality software in less time while simultaneously fulfilling the goals and expectations of the customer by concentrating on different success factors.

A survey on secure metadata of agile software development process using blockchain technology

AbstractScrum is an important and essential technique for developing software. Scrum framework is a project management technique that can emphasize software development teamwork. If you are starting, consider scrum as a method for accomplishing tasks as a team in manageable chunks simultaneously, with ongoing experimentation and feedback loops to learn and improve as you go. Scrum enables individuals and groups to collaboratively and gradually generate value. Being an agile framework, scrum gives people and teams the perfect structure to fit into their workflows while still including the best practices to cater to their requirements. There are some important considerations for security in the agile software development process such as threat modeling, secure coding practices, continuous security testing, authentication, and authorization. In this work, we reviewed various scrum developing techniques to find out the research gaps. This article consider the scrum technique with blockchain technologies for review because it is preferred by most of the software industries.

Activities and Practices of Requirements Engineering in Agile Software Environments

Requirements are one of the important factors for software success. However, Requirements Engineering (RE) activities, in the Waterfall process model, are done sequentially in the analysis phase, which makes it difficult when RE practitioners think and reason about them in Agile Software Development (ASD) process model. RE practitioners need to find the established RE activities conventions in the ASD process model, especially with an increase of software companies, which transform to the ASD process model, in order to foster their transition to the new model. The objective of this study is to provide RE activities in ASD to allow RE practitioners to utilize the appropriate activity for specific ASD methodology. RE activities in ASD are handled repetitively and on a small scale, which makes them embedded in the development life cycle. This paper focuses on highlighting them in different ASD methodologies and discusses the practices that resolve the traditional Waterfall model issues. Although the ASD model has resolved some traditional RE issues, it introduced other issues, such as a consequence of trying to achieve an adequate balance between agility and stability. In addition, there is a lack of practices that target non-functional requirements.

Agile software engineers’ affective states, their performance and software quality: A systematic mapping review

Nowadays, software development companies use agile methodologies to increase the speed and flexibility required by unpredictable working environments and streamline the software delivery process. Agile methodologies emphasize the software engineers’ interactions rather than rigid software development processes. Therefore, agile software development processes (e.g., implementing user stories) should consider software engineers’ affective states since these influence agile software project activities (e.g., team composition or decision-making). We conducted a systematic mapping review following the guidelines of Petersen, K. and Kitchenham, B. to answer our research question: “What affective states influence agile software engineers’ performance and developed software quality?”. We retrieved over 16,000 articles published between January 2010 and September 2021 and after applying selection criteria, 24 primary articles were identified. The results show that the affective states of software engineers influence the activities of the software project and the software development process. Furthermore, we found that there is a lack of well-defined and standard metrics to study the influence of software engineers’ affective states on their performance and the quality of the resulting software. Finally, we concluded that studying and understanding the affective states of software engineers in agile environments is crucial to achieve their well-being at work and improve their performance.

Agile Methods For Improved Cyber Operations Planning

Cyber Ranges provide an interactive simulated environment of hardware and software for simulation. This closed environment provides a safe and legal environment where cyber warfighters can refine their skills. They enable mock cyber mission rehearsal of operation playbooks. Simulated cyber capabilities in the cyber range parallel the intelligence, surveillance, and reconnaissance (ISR), Order of Battle (OOB), and battle damage assessment (BDA) in a closed, safe environment for experimentation. Scrum has been used in collegial cyber competitions with success because it has allowed Capture-the-Flag cyber games to create quicker simulations. Defense Innovation Units (DIUs) are using agile Scrum processes to numerous warfighting areas in order to make them more agile. This research argues that the agile software development processes could be used to optimize the planning and execution of offensive, defensive, and operation and maintenance (O&M) of cyber warfare simulations within cyber ranges. O&M can be done quicker, new exploitable modules can be includer more rapidly, and the capability can be reconstituted to the appropriate skill level for the next set of trainees quicker. The White team as maintainers of the networks, systems, applications and cyber tools select the CVE exploits and spend an enormous amount of time installing and configuring these capabilities for the next set of trainees. Quite often, there are different skill levels which require multiple builds and the ability to refresh the cyber range with varying levels of cyber trainee complexity. This requirement to restore the cyber range quickly with a variety of builds, varying levels of difficulty, and ensure the experiential learning is maximized with the best availability lends to agile methods such as Scrum could lend to improvements with cyber operations. This research will illustrate how a cyber range could leverage agile Scrum processes to provide an improved cyber range environment quicker and with more capabilities.

Perceived Importance of Metrics for Agile Scrum Environments

Metrics are key elements that can give us valuable information about the effectiveness of agile software development processes, particularly considering the Scrum environment. This study aims to learn about the metrics adopted to assess agile development processes and explore the impact of how the role performed by each member in Scrum contributed to increasing/reducing the perception of the importance of these metrics. The impact of years of experience in Scrum on this perception was also explored. To this end, a quantitative study was conducted with 191 Scrum professionals in companies based in Portugal. The results show that the Scrum role is not a determining factor, while individuals with more years of experience have a higher perception of the importance of metrics related to team performance. The same conclusion is observed for the business value metric of the product backlog and the percentage of test automation in the testing phase. The findings allow for extending the knowledge about Scrum project management processes and their teams, in addition to offering important insights into the implementation of metrics for software engineering companies that adopt Scrum.

Requirements engineering for sustainable software systems: a systematic mapping study

Various approaches toward the development of sustainable software systems have been proposed by the requirements engineering community over the last decade. We conducted a systematic mapping study, analyzed 55 publications, and identified 29 approaches that have been published since the year 2000. We analyzed how the approaches evolved over time and how the publications and authors are influenced by each other. Furthermore, the approaches are analyzed in terms of their supported requirements engineering activities, along with the evidence provided in the publications. Additionally, we also analyzed which sustainability definitions have been used, if an iterative application of the approaches is discussed, and if the approaches also provide a tool-support for practitioners. We noticed an increase of publications on requirements engineering approaches toward sustainability in the last years, whereas a majority discuss sustainability based on the same multi-dimensional concept. Although different case studies have been already conducted, we noticed a lack of an industrial application. Our main findings concern the need of an evaluation on how the proposed requirements engineering approaches can also be applied in agile software development processes. Additionally, we also promote the development of supporting software tools to support practitioners in adapting the proposed approaches.

Implementing Quality Assurance in an Agile Software Development Process

Implementing Quality Assurance in an Agile Software Development Process

CAVITE STATE UNIVERSITY – TANZA CAMPUS COMPUTER LABORATORY FINGERPRINT LOG-IN SYSTEM

The Cavite State University – Tanza Campus computer laboratory fingerprint log-in system was developed to monitor and control the use of computers in the laboratory. The study was specifically conducted to determine the features that should be included in the system; evaluate the system in terms of functionality, reliability, usability, efficiency, maintainability, and portability; and determine if the developed system will help in the maintenance of the computer laboratory as perceived by faculty members concerned. The researcher used the agile software development process to develop the system. Through the self-administered questionnaires, necessary information was collected from faculty members and students. After the system was created, it was prepared for end-users evaluation. A total of 89 participants, of which three were faculty members and 86 were students, rated the system according to its functionality, reliability, usability, efficiency, maintainability, and portability. The faculty members who utilized the computer laboratory must provide their full name, employee number, designation, and the department where they belong. They must also provide their fingerprint so as to log in before the use of the laboratory. An alternative log-in module is provided such that the faculty members have to provide their username and password. On the other hand, students must provide their student number, full name, curriculum year, and course. The system features are blocking of programs, commands, and message sending, time limiting of a program that is being used, and file transfer. It also has a database for storing the records of authorized users and time logs of each computer user. The participants evaluated the over-all functionality of the system to be excellent; over-all ratings of other criteria such as reliability, usability, efficiency, maintainability, and portability were likewise rated as excellent. Moreover, all the faculty members utilizing the computer laboratory agreed that the developed system will help in the maintenance of the computer laboratory.

Agile software development Process Orientation for eliminating errors as non-value-added activities in food and nutrition industries

Agile software development Process Orientation for eliminating errors as non-value-added activities in food and nutrition industries

DevOps Main Area and Core Capabilities Adopting DevOps in the Last Decade: A Systematic Literature Review

DevOps is a collaboration between software development and operation that utilizes frameworks like continuous integration, microservices, continuous delivery, and continuous deployment for an agile software development process. DevOps has principles like automation, iteration, and continuous release and development. This research aims to know DevOps development in the last decade and know how potentially adopt the DevOps development process. This study uses the Systematic Literature Review (SLR) method to locate, evaluate, and summarize pertinent works that were published in the public domain between 2012-2022. The result of this review will be used by researchers and practitioners as a piece of knowledge about the DevOps core capabilities and main areas of DevOps from adopting DevOps in the last decade.

Development of an mHealth Platform for Adolescent Obesity Prevention: User-Centered Design Approach.

Obesity is a chronic condition that influences the quality of life of patients and families while increasing the economic burden for the world population. Multidisciplinary prevention programs are crucial to address it, allowing an early introduction of healthy behaviors into daily habits. Mobile health interventions provide adequate support for these programs, especially considering the gamification techniques used to promote users’ engagement. TeenPower is a multidisciplinary mHealth intervention program conducted in Portugal during 2018 to empower adolescents, promoting healthy behaviors while preventing obesity. An agile software development process was applied to the development of the digital platform that holds a web-based application and a mobile application. We also propose a model for future developments based on the user-centered design approach adopted for this development and the assessment conducted in each phase. The user-centered design approach model proposed has three distinct phases: (1) design study; (2) pre-production usability tests; and (3) post-production data. Phase 1 allowed us to obtain the high-fidelity version of the graphical user interfaces (n = 5). Phase 2 showed a task completion success rate of 100% (n = 5). Phase 3 was derived from statistical analysis of the usage of the platform by real end users (n = 90). We achieved an average retention rate of 35% (31 out of 90 participants). Each technique has provided input for the continuous design and improvement of the platform. This allowed the creation of a tailored platform that could meet users’ expectations. Nevertheless, the retention rate decreased significantly over a short period of time, revealing the need for further work in the improvement of the gamification experience.

The use of Design Science and Agile Methodologies for improved information systems in the Tanzanian Higher Education context

AbstractThere was no known effective approach to implementing information systems in Tanzanian Higher Education Institutions (HEIs) because the requirements of users change frequently and HEIs vary in their requirements. Theoretically, the agile software development process and Design Science Research (DSR) could deliver software that suits such a context, yet no testing had been done priorly. Therefore, this study aimed on investigating the suitability of the combination of Agile Methodologies and the DSR in developing information systems for Tanzania's HEIs. The study used eXtreme Programming as one of the Agile Methodologies and the DSR to develop a timetabling software which easily integrates into the existing academic information system of the College of Business Education for better decision making. Likewise, the evaluation of the developed artifact confirmed that the resulting product raised the user satisfaction with the information system in HEIs. In this regard, the current study advances the frontier of knowledge on using the DSR framework and Agile Methodologies in designing and developing software in Tanzania's HEIs and beyond.

A "No-Code" App Design Platform for Mobile Health Research: Development and Usability Study.

BackgroundA challenge facing researchers conducting mobile health (mHealth) research is the amount of resources required to develop mobile apps. This can be a barrier to generating relevant knowledge in a timely manner. The recent rise of “no-code” software development platforms may overcome this challenge and enable researchers to decrease the cost and time required to develop mHealth research apps.ObjectiveWe aimed to describe the development process and the lessons learned to build Pathverse, a no-code mHealth app design platform.MethodsThe study took place between November 2019 and December 2021. We used a participatory research framework to develop the mHealth app design platform. In phase 1, we worked with researchers to gather key platform feature requirements and conducted an exploratory literature search to determine needs related to this platform. In phase 2, we used an agile software framework (Scrum) to develop the platform. Each development sprint cycle was 4 weeks in length. We created a minimum viable product at the end of 7 sprint cycles. In phase 3, we used a convenience sample of adults (n=5) to gather user feedback through usability and acceptability testing. In phase 4, we further developed the platform based on user feedback, following the V-model software development process.ResultsOur team consulted end users (ie, researchers) and utilized behavior change technique taxonomy and behavior change models (ie, the multi-process action control framework) to guide the development of features. The first version of the Pathverse platform included features that allowed researchers to (1) design customized multimedia app content (eg, interactive lessons), (2) set content delivery logic (eg, only show new lessons when completing the previous lesson), (3) implement customized participant surveys, (4) provide self-monitoring tools, (5) set personalized goals, and (6) customize app notifications. Usability and acceptability testing revealed that researchers found the platform easy to navigate and that the features were intuitive to use. Potential improvements include the ability to deliver adaptive interventions and add features such as community group chat.ConclusionsTo our knowledge, Pathverse is the first no-code mHealth app design platform for developing mHealth interventions for behavior. We successfully used behavior change models and the behavior change technique taxonomy to inform the feature requirements of Pathverse. Overall, the use of a participatory framework, combined with the agile and hybrid-agile software development process, enabled our team to successfully develop the Pathverse platform.

WEB-BASED ONLINE MOTORBIKE DEALING SYSTEM

Motorbikes are an essential mode of transportation in Indonesia. People utilize it on a regular basis to get to work, school, and to transfer goods. According to data from Badan Pusat Statistik, the number of motorbikes in Indonesia hit 112 million units in 2019 [1]. Because of the high demand for motorbikes in Indonesia, many individuals must rely on loans. This, in turn, leads to a rise in fraud cases because people alter paperwork. Increasing fraud incidences by faking identities and documents. Aside from the possibility of fraud, there is also the long process that customers must endure by coming to the showroom, waiting for the list, and following a series of inefficient processes, so that the customers waste their time by doing those activities that cause them to miss other activities that are more productive. Customers may minimize time-wasting activities and fraud as much as feasible by establishing this online system. Because of these issues, this paper will present a web-based system that can assist clients, leasing companies, and dealers in online transactions to ensure that all provided documents are authentic. The system was developed in the website so that can be accessed in both mobile and personal computer. The website will be made based on agile software development process called rapid application development (RAD). Finally, the Web-based online motorbike dealing system has been developed and tested to meet a whole motorbike sales business process properly without any faults, flaws, or issues. Further research will mainly talk about automatic document verification and security issue.

How agile coaches create an agile mindset in development teams: Insights from an interview study

AbstractSince the publication of the agile manifesto in 2001, many companies implement an agile—or at least more agile—software development process. However, only including agile methods or practices in the overall process does not guarantee being agile. The mindset of the people involved in the process, including the development team, the customers, and the management, is of particular importance. As such an agile mindset cannot be enforced, the process of creating a suitable mindset needs to be handled with care. In an interview study with nine agile coaches, we analyzed which aspects they perceive being of particular importance during an agile transformation. One of these aspects is the agile mindset. We figure out how they support the creation of such a mindset. We identify 12 categories related to the process of creating an agile mindset. These categories include the collaboration between the coach and the management as well as the necessity to internalize the agile values. The main factor for succeeding with the creation of an agile mindset, however, can be hardly influenced: The success strongly depends on the personal prerequisites and attitudes of the individuals involved in the process, mainly the development team. We synthesize the results of our study into a timeline describing the process of how an agile coach can support the development team creating an agile mindset as part of the transformation towards an agile development process.

Empowered and embedded: ethics and agile processes

This article focuses on the structural aspects of the development of ethical software, and argues that ethical considerations need to be embedded into the (agile) software development process. In fact, it is claimed that agile processes of software development lend themselves specifically well for this endeavor. First, it is contended that ethical evaluations need to go beyond the use of software products and include an evaluation of the software itself. This implies that software engineers influence peoples’ lives through the features of their designed products. Embedded values should thus also be approached by software engineers themselves. Therefore, the emphasis is put on the possibility to implement ethical deliberations in already existing and well-established agile software development processes. The proposed approach relies on software engineers making their own judgments throughout the entire development process to ensure that technical features and ethical evaluation can be addressed adequately to transport and foster desirable values and norms. It is argued that agile software development processes may help the implementation of ethical deliberation for five reasons: (1) agile methods are widely spread, (2) their emphasis on flat hierarchies promotes independent thinking and autonomy, (3) their reliance on existing team structures serve as an incubator for deliberation, (4) agile development enhances object-focused techno-ethical realism, and, finally, (5) agile structures provide a salient endpoint to deliberation.