Search

The agile approach to software development has significantly impacted the industry, given its ability to cope with requirements. Despite this, many aspects of the agile paradigm's compatibility with various software project characteristics have not been thoroughly researched. To address this lacuna, the study presents a systematic literature review (SLR) that aims to assess the compatibility of the agile methodology with each of the knowledge areas included in the Project Management Body of Knowledge (PMBOK). By employing Machine Learning (ML) text-mining and sentiment analysis techniques, the paper explores the sentiment regarding each PMBOK knowledge area (PM-KA). It thus provides valuable insights to assist practitioners and researchers in assessing the compatibility of the agile methodology with each PM-KA and identifying potential gaps or significant challenges within the agile paradigm. [ABSTRACT FROM AUTHOR]

In the recent years, the advances in mobile technology have brought an exorbitant change in daily lifestyle of individuals. Smartphones/mobile devices are rampant in all aspects of human life. This has led to an extreme demand for developing software that runs on mobile devices. The developers have to keep up with this high demand and deliver high-quality app on time and within budget. For this, estimation of development and testing of apps play a pivotal role. In this paper, a Systematic Literature Review (SLR) is conducted to highlight development and testing estimation process for software/application. The goal of the present literature survey is to identify and compare existing test estimation techniques for traditional software (desktop/laptop) and for mobile software/application. The characteristics that make mobile software/application different from traditional software are identified in this literature survey. Further, the trend for developing the software is towards agile, thus this study also presents and compares estimation techniques used in agile software development for mobile applications. The analysis of literature review suggests filling a research gap to present formal models for estimating mobile application considering specific characteristics of mobile software. [ABSTRACT FROM AUTHOR]

Uncertainty has become a challenge in project management during the age of the Covid-19 pandemic. Project management required a more flexible and dynamic approach; therefore, it is believed that Agile project management could provide a solution to this problem. Agile has been widely used in multiple industry areas as a practical and flexible approach in project management practices. In the project, the scope is considered one aspect that can directly affect the budget and timing. Unfortunately, it seems to be one of the most neglected domains in Agile and conventional. Agile is recognized for its rapid improvement as well as its willingness to embrace change. However, uncontrolled change can potentially delay and make the project overspend. This paper aims to examine the challenges and discover the best practices in handling scope and change in Agile. A systematic literature review (SLR) was carried out through the literature sources, which entailed IEEE Explore, ScienceDirect, Emerald Insight, ProQuest, and Wiley Online. The finding was seven categories, and eighteen issues were found. Then twenty-four best practices were mapped to the challenges. We found the most significant challenge came from People & Organization, User Requirement Prioritization, Over-scope Requirement, and Communication & Coordination. Those areas are considered the most significant challenge because they can create delays and overspend in the project. [ABSTRACT FROM AUTHOR]

This paper presents a systematic literature review of agile software development at decision making method for requirement engineering. Presently, agile software development method is operated to cope with requirements that changes dynamically. This study seeks to find out and discuss what types of method that have been exploited for decision making on managing feasible requirements and challenges of decision making in agile software development. Papers reviewed in this study are published from 2017 to present. Resulting 8 papers that have been identified of presenting decision making methods. Using these papers, 11 methods and 7 challenges of decision making identified. This study contributes a review of requirement management and engineering by providing decision making methods on agile software development and the challenges of decision making for requirement engineering. [ABSTRACT FROM AUTHOR]

Highlights • Mostly of the selected studies analyzed neglected the quality criteria and have difficulties to use methods to synthetize the research results. • The integration of usability with agile software development is possible and is strongly aligned with user-centered design. • Most studies are interested in investigating this relation and the viability of this integration, but there is no consensus established about how to integrate them. Abstract In the last years the interest in developing research on integration of usability and agile software development has been increasing. The number of systematic literature reviews, systematic mapping studies and non-systematic reviews, related to this thematic has also increased. Nevertheless, there is no analysis on the quality of these published secondary studies, nor is there a consolidated research that brings the answer of how to integrate these two areas. The goal of this paper is to categorize secondary studies related to the integration of usability and agile software development and present a critical analysis on the quality of the selected studies. To accomplish this goal a tertiary study was performed to categorize the related studies selected. Initially 3,065 papers were identified and further narrowed to 14 by applying exclusion criteria and analysis. We classified the selected studies as systematic literature reviews, systematic mapping studies and non-systematic literature reviews to report the data analysis. As a result of this study different forms to integrate usability and agile software development were detected as well as the various challenges that must be overcome for the integration success. Six main categories were identified to represent ways of integrating usability into agile development: processes, techniques, practices, recommendations, principles and different approaches. Regarding to the challenges for the integration seven main categories were also identified: issues related to tests, time, work balance, modularization, feedback, prioritization, and documentation. Although the interest in researching the integration of usability and agile software development has increased in the last years, mostly of the analyzed studies neglected the quality criteria and presented difficulties to use methods to synthetize the research results. Despite this, it has been realized that the integration of usability with agile software development is possible and is strongly aligned with user-centered design. The initial studies indicated a separation of activities and roles into specific tracks with parallel work to treat usability in agile software development, but the trend is no longer to manage and control these activities in separate ways, so new challenges are becoming to appear. Although we have identified several points of tension, the integration does not become unfeasible. [ABSTRACT FROM AUTHOR]

Nowadays, Agile Software Development (ASD) is used to cope with increasing complexity in system development. Hybrid development models, with the integration of User-Centered Design (UCD), are applied with the aim to deliver competitive products with a suitable User Experience (UX). Therefore, stakeholder and user involvement during Requirements Engineering (RE) are essential in order to establish a collaborative environment with constant feedback loops. The aim of this study is to capture the current state of the art of the literature related to Agile RE with focus on stakeholder and user involvement. In particular, we investigate what approaches exist to involve stakeholder in the process, which methodologies are commonly used to present the user perspective and how requirements management is been carried out. We conduct a Systematic Literature Review (SLR) with an extensive quality assessment of the included studies. We identified 27 relevant papers. After analyzing them in detail, we derive deep insights to the following aspects of Agile RE: stakeholder and user involvement, data gathering, user perspective, integrated methodologies, shared understanding, artifacts, documentation and Non-Functional Requirements (NFR). Agile RE is a complex research field with cross-functional influences. This study will contribute to the software development body of knowledge by assessing the involvement of stakeholder and user in Agile RE, providing methodologies that make ASD more human-centric and giving an overview of requirements management in ASD. [ABSTRACT FROM AUTHOR]

With the rise of agile development notion, software test automation is widely adopted by software organizations to reduce the testing time and costs during the software development process. However, it is essential to carefully implement the test automation to ensure the project's success. In the literature, several studies have indicated that decision-making is crucial for the adoption of test automation. For deciding about test automation adoption, several factors, including the skill level of testers, test tool, and development process, need to be considered since automated testing performance heavily depends on the mentioned factors and their interactions. Thus, it is of vital importance to ascertain the factors that influence test automation in the context of Agile-based Software Development (ASD). To accomplish this, we perform a systematic literature review and a questionnaire-based survey. In total, 21 factors are identified that significantly impact test automation in the ASD context. Additionally, the identified factors are categorized into five main classes. Following the identified factors' assessment, this work proposes a conceptual model that supports agile practitioners in deciding about the adoption of test automation in the context of ASD. Finally, this work validates the proposed model to assess its practical applicability. The validation of the proposed model is accomplished by using an expert-based validation approach. The attained results show that the proposed model supports agile practitioners in estimating the possibility of success when implementing test automation in the ASD context. [ABSTRACT FROM AUTHOR]

As many software development teams have started to adopt agile methods, a vast amount of valuable experiences have been reported on in both academic and industrial knowledge bases. This information has been used through various approaches to guide and help practitioners finding suitable practices for their software development projects. Nevertheless, not many of these approaches could gather the available experiences to make them systematically reusable and help practitioners understanding agile practices in depth. To the best of our knowledge, only one ontology has been created to solve this problem; some limitations related to its quality and usability make it nevertheless unqualified to serve the intended purpose. The aim of this paper is to build an expert system (i.e. an evidence-based tool) to ease agile practices adoption by efficiently and effectively providing information on them. Firstly, we improve the concepts and relationships in the aforementioned ontology and theoretically validate it using a large data-set of agile practices adoption experiences collected through a Systematic Literature Review (SLR). Secondly, we develop a supporting tool having a friendly Graphical User Interface (GUI) allowing to use the ontology as a concrete agile practice knowledge provider. Finally, we empirically validate the enhanced ontology and evaluate the supporting tool using a survey with agile experts. Our supporting tool can help practitioners to decide what practice to adopt, how to adopt it, how to solve practical issues, etc. The ontology and the tool materialize our contribution to the field of systematic agile practices adoption. • Successful agile practice adoption requires an in depth understanding of its content. • Existing reports on agile practice adoption experiences are essentially unexploitable. • An ontology is used as an efficient solution to recycle practices adoption experience. • A corpus-based approach and a survey are used for validating the ontology. • An expert system supports practitioners querying knowledge on practice adoption. [ABSTRACT FROM AUTHOR]

• Systematic Literature Review about Metamodel-Based Simulation Optimization (MBSO). • The integration of new machine learning tools could improve metamodels. • The main applications, concepts and state of the art in MBSO were discussed. • The research found and discussed gaps that can be addressed by future studies. Over the past few decades, modeling, simulation, and optimization tools have received attention for their ability to represent and improve complex systems. The use of metamodeling techniques in optimization via simulation problems has grown considerably in recent years to promote more robust and agile decision-making, determining the best scenario in the solution space. The objective of this article is to conduct a systematic literature review of metamodeling-based simulation optimization (MBSO). The main contributions of this paper are related to systematically gather, analyze, and discuss the knowledge disseminated in this area, support future research and expand the literature related to MBSO techniques. Research questions were planned to assist MBSO researchers and practitioners, by presenting the most frequent contexts, applications, methods, tools, and metrics found in metamodeling studies in optimization via simulation problems. We considered papers published in scientific journals and listed in the Web of Science, Scopus, ACM Digital Library, IEEE Xplore, and Science Direct databases. The conclusion related the gaps, opportunities, and future perspectives found during the development of this research, suggesting that this research area is growing in the past 15 years. [ABSTRACT FROM AUTHOR]

• The paper presents a review of 45 studies related to software risk in the context of the software life cycle. • A large number of studies reviewed involve other knowledge areas to support decision-making in the risk management activities. • A few proposals for risk management use internationally recognised standards or de facto models to its definition. • It is especially important to define a framework and model for risk management in the software life cycle using an agile approach. • It is important that agile approaches include risk management practices which are in line with the already accepted ones in traditional approaches. Risk management (RM) plays a key role in project management, as it allows identification and prompt management of threats that may arise during project execution. Furthermore, project management within the software industry is evolving rapidly nowadays, a fact that implies new challenges, because the emergence and use of fresh approaches has brought a greater degree of complexity to the RM process. The objective of this paper is to carry out a systematic literature review (SLR) in the field of software risk, in an attempt to characterize and present the state of the art of this field, identifying gaps and opportunities for further research. From the analysis of the results of this SLR it could be observed that interest on the part of the scientific community has turned away from the definition of research work that addressed an integrated risk management process, to pay attention to work that concentrates on specific activities of this process. It was also possible to see that there is a clear lack of scientific rigour as regards the process of validation in the different studies, and a deficiency in the use of standards or of de facto models to define these. [ABSTRACT FROM AUTHOR]