Choice of Agile Methodologies in Software Development: A Vendor Perspective

The purpose of this research was to develop understanding about how vendor firms make choice about agile methodologies in software projects and their fit. Two analytical frameworks were developed from extant literature and the findings were compared with real world decisions. Framework 1 showed that the choice of XP for one project was not supported by the guidelines given by the framework. The choices of SCRUM for other two projects, were partially supported. Analysis using the framework 2 showed that except one XP project, all others had sufficient project management support, limited scope for adaptability and had prominence for rules

Key Factors for Selecting an Agile Method: A Systematic Literature Review

Agile methods have become popular in recent years because the success rate of project development using Agile methods is better than structured design methods. Nevertheless, less than 50 percent of projects implemented using Agile methods are considered successful, and selecting the wrong Agile method is one of the reasons for project failure. Selecting the most appropriate Agile method is a challenging task because there are so many to choose from. In addition, potential adopters believe that migrating to an Agile method involves taking a drastic risk. Therefore, to assist project managers and other decision makers, this study aims to identify the key factors that should be considered when selecting an appropriate Agile method. A systematic literature review was performed to elicit these factors in an unbiased manner and then content analysis was used to analyze the resultant data. It was found that the nature of project, development team skills, project constraints, customer involvement and organizational culture are the key factors that should guide decision makers in the selection of an appropriate Agile method based on the value these factors have for different organizations and/or different projects

A Review of Mobile Application Development in the Agile Software Development Environment

With the ever changing dynamic environment in mobile devices, mobile software applications need to cope with some particular performance environment that include the limited resources, high autonomy requirements and mark et regulations among other constraints [1]. To provide a software development process that responds to these challenges, adoption of Agile methodology that follows an iterative approach to build software rapidly where the entire software development lifecycle is brok en down into smaller iterations helps to minimize overall risk s. This allows software projects developed though agile methodologies to be easily modified rapidly to meet the users/customers’ requirements. This paper assesses the development of mobile applications in the agile software development environment

A Feature-Based Tool-Selection Classification for Agile Software Development

Abstract-With the advancement in technology, software development complexities are rising across the globe. This trend is forcing companies and organizations to adopt management methods and tools to accelerate time to market, more easily manage changing priorities, increase the customer satisfaction and reduce product expenses. Agile software development methods offer a solution to these issues, but problems remain over evaluation along with the offering of the correct agile software as well as a collection of agile tools. The purpose of this paper is to introduce best tools and features, criteria used for evaluating currently existing tools and propose a classification model to right agile tool selection. To prepare a list of the best tools and their features in the market, a practical research on existing tools and their features were performed. Finally, a classification model was prepared and the results show which tools best fit into different level of maturity in projects and companies

Modern Code Reviews: Preliminary Results of an Analysis of the State of the Art with Respect to the Role Played by Human Factors

Modern Code Reviewing has shown to be an effective mechanism to identify bugs in the code; however, given their intrinsic subjectivity, they can be significantly affected by human factors such as interpersonal relationships. This paper focuses on exploring such issues, with specific attention to social iterations and personal factors. Future work includes experimental evaluations to verify the research hypothesis related to improving the quality of the process under the study

Challenges and opportunities of low-code platforms for software development

The current energy and climate crisis emphasize the energy-efficiency knowledge gap as a pressing problem. This is addressed in the report and the mobile application called EnMo, which was developed as part of this field lab. Topics regarding gamification, big data analytics, and low-code development were investigated. The findings provide the foundation for developing the app and its mission as a solution to the problem. EnMo incentivizes users to reduce their household energy consumption, by collecting user information and providing educational and gamified content. Thus, EnMo enables consumers to change their behavior and reduce their energy-efficiency knowledge gap. This exposition discusses the challenges and opportunity of low-code platforms for software development specifically. While speedy development, low maintenance and cost as well as low transparency and customization were filtered out as advantages of low-code, potential vendor lock-ins, black box issues and the fear of replacing software developers might present pitfalls of the technology

A model-based approach to systematic reviews of research literature

A systematic approach to develop a literature review is attractive because it aims to achieve a repeatable, unbiased and evidence-based outcome. However the existing form of systematic review such as Systematic Literature Review (SLR) and Systematic Mapping Study (SMS) are known to be an effort, time, and intellectual intensive endeavour. To address these issues, this paper proposes a model-based approach to Systematic Review (SR) production. The approach uses a domain-specific language expressed as a meta-model to represent research literature, a meta-model to specify SR constructs in a uniform manner, and an associated development process all of which can benefit from computer-based support. The meta-models and process are validated using real-life case study. We claim that the use of meta-modeling and model synthesis lead to a reduction in time, effort and the current dependence on human expertise