Search

Context: The complexity of modern economic processes, along with the pressure from competition, the increasing client expectations and the need to introduce changes in the course of project implementation have led to a great interest in agile management methods. Therefore, the answer the question whether the implementation of an agile approach to project management can contribute to the project success is gaining relevance in a changing and inconsistent environment. Objective: This study attempts to answer the question which aspects of agility and in what manner can influence the final outcome of project work? The underlying objective of the study was to identify the conditions and success factors of implemented projects. Method: This paper presents the results of a survey conducted in companies in ICT sector. For this purpose, a number of reports and materials provided by organisations and associations dealing with project management issues, in particular ICT projects, were analysed, complemented with data obtained from statistical offices and financial institutions. For the purposes of the own study, an original questionnaire was developed to identify critical factors for project success, in particular the defined agile components. Results: On the basis of the conducted survey it can be concluded that the presence and high level agility is conducive to successful projects. It is the high level of agility supporting project activities that is essential for success. Of no less importance are the people and interactions between them, as well as self-organising teams. They are crucial for a positive evaluation of the project activities. Conclusions: Identification of the relationship between selected agility components and project success components allowed recommendations for solutions and attitudes that increase the chances of success in project management to be formulated. The synergy of individual agile components applied that increases the chances for project success. [ABSTRACT FROM AUTHOR]

Early effort estimation is important for efficiently planning the use of resources in an Information Technology (IT) project. However, limited research has been conducted on the topic of effort estimation in agile software development using artificial intelligence. This research project contributes to strengthening the use of hybrid models composed of algorithmic models and learning oriented techniques as a project-level effort estimation method in agile frameworks. Effort estimation in agile methods such as Scrum uses a story point approach that measures, using an arithmetic scale, the effort required to complete a release of the system. This project relied on labeled historical data to estimate the completion time measured in days and the total cost of a project set in Pakistani rupees (PKR). using a decision tree, random forest and AdaBoost to improve the accuracy of predictions. Models were trained using 10-fold cross-validation and the relative error was used as a comparison with literature results. The bootstrap aggregation (bagging) ensemble made of the three techniques provides the highest accuracy, and project classification also improves the estimates. [ABSTRACT FROM AUTHOR]

Crowdsourcing is an emerging approach in software development, where software is developed by unknown, heterogeneous people around the globe, via an open call by the employer. Crowdsourcing, when used with agile, faces challenges because of the different development methodologies. Agile development methodology has practices that involve face-to-face frequent interaction, whereas crowdsourcing is a distributed development with no or limited face-to-face interaction. Both concepts are actively being used in the software development industry due to their benefits. However, there is a need to explore the integration of both methodologies for an effective and efficient software development. In this regard, the first step is to identify the challenges of integrating crowdsourcing and agile. In this paper, we intend to identify the possible challenges that may be faced while executing agile along with crowdsourcing. For this, we have conducted a Systematic Literature Review. Five main categories of challenges are presented which are: team issues, coordination and communication issues, organizational issues, project-related issues and task-related issues. A list of possible challenges of Agile–Crowd Software Development (ACSD) is presented in this study. [ABSTRACT FROM AUTHOR]

Today, the economic crisis is putting enormous pressure on most organizations. It evolves in a crucial competitive environment with a multiplication of production cycles and implementation on the market. Due to this dynamism, organizations must be scalable and agile by adopting an approach that aims to make the process model of a given organization reusable. Indeed, according to the new paradigm which is called "Design by reuse" the models of configurable processes, gain recently in importance since these models have the capacity to represent explicitly the common parts and variables of identical processes in a customizable model. These configurable process which group several execution choices through a variation point called configurable connector will present an uncertainty related to the execution (or not) of the conditional tasks in a process model. In this paper, we propose a measure based on Shannon's entropy in order to model the uncertainty of the process at design time to guide configurable business process designers and analysts in developing and improving processes to be more predictable, less complex, and more understandable. [ABSTRACT FROM AUTHOR]

Daily stand-up meetings (DSMs) are the most popular technique in agile methodologies and are deemed crucial for communication among the individual agile software developers to perform. Only a handful of studies in the past have shown the effect of the characteristics of DSMs on the attitude of agile developers. Little is known about how agile developers experience DSMs in their roles as junior/senior developers, and what feelings evoke these experiences. The purpose of this study was to describe and interpret agile developers' lived experiences with DSMs in their diverse roles. We conducted a hermeneutic phenomenological study with 19 professional agile developers. The lived experiences across the interviews revealed as an interaction between four categories: rationalising irrelevancy of DSMs, experiencing challenges with DSMs, conflicted opinion on the advantages of DSMs, and finding solutions. Developers experienced DSMs were too short to facilitate clear problem identification, or solve problems, or have a meaningful outcome. Senior developers experienced DSMs differently than junior developers in terms of sharing information, interest in other's work, monitoring progress, and facilitating decision making. Based on these findings, we discuss the theoretical contributions of our study, and offer recommendations for practitioners. [ABSTRACT FROM AUTHOR]

Computation intelligence techniques are important for making decisions in an agile-based offshore software development paradigm. Offshore development faces additional challenges, such as trust, communication and coordination, and socio-cultural and knowledge transfer. There is a need to determine the rankings of challenges considering their criticality concerning practitioners working in agile-based offshore software development. This paper aims to identify and rank agile challenges in offshore software development by applying computational intelligence techniques. From the systematic literature review, we identified 30 communication and coordination challenges. The distributed agile pattern catalog consists of 15 patterns, from which eight were used to solve communication and collaboration challenges. Many researchers have used fuzzy logic to quantify their results. We further applied the fuzzy analytical technique to determine the priority order concerning the criticality of the identified agile pattern catalog. The results showed that Central Code Repository Pattern ranked the most significant for solving communication and coordination challenges. Global Scrum Board Pattern and Synchronous Communication Pattern ranked second. [ABSTRACT FROM AUTHOR]

With years of frantic development, when release fast and release often was the mandatory rule for web technologies and services, the open source paradigm and online distribution repositories have imposed de facto standards for quality assessment in fast‐paced innovation processes. Nowadays, however, in pursuit of productivity, security, and user satisfaction, the industry is beginning, through the introduction of new standards such as ECMAScript 6 or web components, to consider software engineering mandates for web technologies. This article reports a quality model aligned with international standard ISO/IEC 25010, covering web components technology, which ultimately aims to improve adoption by the software engineering industry, traditionally wary of agile Internet practices, the open source paradigm, and public repositories. Our research also presents an experimentation platform on which end users have validated the quality properties, highlighting the implicit connection with the perceived quality. The key result of our research convinces us that user ratings are suitable as a testing mechanism for product quality and quality‐in‐use metrics in order to define an absolute scale of comparison for web component quality. [ABSTRACT FROM AUTHOR]

Frequency hopping spread spectrum (FHSS) applies widely to communication and radar systems to ensure communication information and channel signal quality by tuning frequency within a wide frequency range in a random sequence. An efficient signal processing scheme to resolve the timing and duration signature from an FHSS signal provides crucial information for signal detection and radio band management purposes. In this research, hopping time was first identified by a two-dimensional temporal correlation function (TCF). The timing information was shown at TCF phase discontinuities. To enhance and resolve the timing signature of TCF in a noisy environment, three stages of signature enhancement and morphological matching processes were applied: first, computing the TCF of the FHSS signal and enhancing discontinuities via wavelet transform; second, a dual-diagonal edge finding scheme to extract the timing pattern signature and eliminate mismatching distortion morphologically; finally, Hough transform resolved the agile frequency timing from purified line segments. A grand-scale Monte Carlo simulation of the FHSS signals with additive white Gaussian noise was carried out in the research. The results demonstrated reliable hopping time estimation obtained in SNR at 0 dB and above, with a minimal false detection rate of 1.79%, while the prior related research had an unattended false detection rate of up to 35.29% in such a noisy environment. [ABSTRACT FROM AUTHOR]

Nowadays, Internet applications with different network resource requirements have been growing exponentially; therefore, the network equipment needs to be configured consistently based on application resource requirements. In this paper, Software Defined Network (SDN) is used to make the network more programmable, flexible and agile to develop the proposed model. Flow discrimination and optimized resource allocation are significant and challenging items in providing the required network resources for each flow. In this paper, we propose a model composed of (1) network flows' types discriminator and (2) the optimized resource allocation based on the flow classes. The applications are clustered into four groups according to the network resource requirements, and a deep network traffic discriminator is used for classification. The greedy algorithm is also used for optimized resource allocation. The proposed model is developed in Mininet with a Pox controller to prove Quality of Service (QoS) improvement paralleled with maximized utilization. The simulation results show that the proposed model has intelligent behaviour in network resource allocation based on flows' requirements compared to Spanning Tree Protocol (STP) and Dynamic and Adaptive Multipath Routing (DAMR) while maximizing the network utilization. [ABSTRACT FROM AUTHOR]

To protect New Zealand's unique ecosystems and primary industries, imported plant materials must be constantly monitored at the border for high-threat pathogens. Techniques adopted for this purpose must be robust, accurate, rapid, and sufficiently agile to respond to new and emerging threats. Polymerase chain reaction (PCR), especially real-time PCR, remains an essential diagnostic tool but it is now being complemented by high-throughput sequencing using both Oxford Nanopore and Illumina technologies, allowing unbiased screening of whole populations. The demand for and value of Point-of-Use (PoU) technologies, which allow for in situ screening, are also increasing. Isothermal PoU molecular diagnostics based on recombinase polymerase amplification (RPA) and loop-mediated amplification (LAMP) do not require expensive equipment and can reach PCR-comparable levels of sensitivity. Recent advances in PoU technologies offer opportunities for increased specificity, accuracy, and sensitivities which makes them suitable for wider utilization by frontline or border staff. National and international activities and initiatives are adopted to improve both the plant virus biosecurity infrastructure and the integration, development, and harmonization of new virus diagnostic technologies. [ABSTRACT FROM AUTHOR]

Throughout the evolution of software systems, empirical methodologies have been used in their development process, even in the Internet of Things (IoT) paradigm, to develop IoT-based systems (IoTS). In this paper, we review the fundamentals included in the manifesto for agile software development, especially in the Scrum methodology, to determine its use and role in IoTS development. Initially, 4303 documents were retrieved, a number that was reduced to 186 after applying automatic filters and by the relevance of their titles. After analysing their contents, only 60 documents were considered. Of these, 38 documents present the development of an IoTS using some methodology, 8 present methodologies focused on the construction of IoTS software, and 14 present methodologies close to the systems life cycle (SLC). Finally, only one methodology can be considered SLC-compliant. Out of 38 papers presenting the development of some IoTS following a methodology for traditional information systems (ISs), 42.1% have used Scrum as the only methodology, while 10.5% have used Scrum combined with other methodologies, such as eXtreme Programming (XP), Kanban and Rapid Prototyping. In the analysis presented herein, the existing methodologies for developing IoTSs have been grouped according to the different approaches on which they are based, such as agile, modelling, and service oriented. This study also analyses whether the different proposals consider the standard stages of the development process or not: planning and requirements gathering, solution analysis, solution design, solution coding and unit testing (construction), integration and testing (implementation), and operation and maintenance. In addition, we include a review of the automated frameworks, platforms, and tools used in the methodologies analysed to improve the development of IoTSs and the design of their underlying architectures. To conclude, the main contribution of this work is a review for IoTS researchers and developers regarding existing methodologies, frameworks, platforms, tools, and guidelines for the development of IoTSs, with a deep analysis framed within international standards dictated for this purpose. [ABSTRACT FROM AUTHOR]

Purpose: The SingHealth-Duke-GlaxoSmithKline COPD and Asthma Real-world Evidence (SDG-CARE) collaboration was formed to accelerate the use of Singaporean real-world evidence in research and clinical care. A centerpiece of the collaboration was to develop a near real-time database from clinical and operational data sources to inform healthcare decision making and research studies on asthma and chronic obstructive pulmonary disease (COPD). Methods: Our multidisciplinary team, including clinicians, epidemiologists, data scientists, medical informaticians and IT engineers, adopted the hybrid waterfall-agile project management methodology to develop the SingHealth COPD and Asthma Data Mart (SCDM). The SCDM was developed within the organizational data warehouse. It pulls and maps data from various information systems using extract, transform and load (ETL) pipelines. Robust user testing and data verification was also performed to ensure that the business requirements were met and that the ETL pipelines were valid. Results: The SCDM includes 199 data elements relevant to asthma and COPD. Data verification was performed and found the SCDM to be reliable. As of December 31, 2019, the SCDM contained 36,407 unique patients with asthma and COPD across the spectrum from primary to tertiary care in our healthcare system. The database updates weekly to add new data of existing patients and to include new patients who fulfil the inclusion criteria. Conclusions: The SCDM was systematically developed and tested to support the use RWD for clinical and health services research in asthma and COPD. This can serve as a platform to provide research and operational insights to improve the care delivered to our patients. [ABSTRACT FROM AUTHOR]

Purpose: The SingHealth-Duke-GlaxoSmithKline COPD and Asthma Real-world Evidence (SDG-CARE) collaboration was formed to accelerate the use of Singaporean real-world evidence in research and clinical care. A centerpiece of the collaboration was to develop a near real-time database from clinical and operational data sources to inform healthcare decision making and research studies on asthma and chronic obstructive pulmonary disease (COPD). Methods: Our multidisciplinary team, including clinicians, epidemiologists, data scientists, medical informaticians and IT engineers, adopted the hybrid waterfall-agile project management methodology to develop the SingHealth COPD and Asthma Data Mart (SCDM). The SCDM was developed within the organizational data warehouse. It pulls and maps data from various information systems using extract, transform and load (ETL) pipelines. Robust user testing and data verification was also performed to ensure that the business requirements were met and that the ETL pipelines were valid. Results: The SCDM includes 199 data elements relevant to asthma and COPD. Data verification was performed and found the SCDM to be reliable. As of December 31, 2019, the SCDM contained 36,407 unique patients with asthma and COPD across the spectrum from primary to tertiary care in our healthcare system. The database updates weekly to add new data of existing patients and to include new patients who fulfil the inclusion criteria. Conclusions: The SCDM was systematically developed and tested to support the use RWD for clinical and health services research in asthma and COPD. This can serve as a platform to provide research and operational insights to improve the care delivered to our patients. [ABSTRACT FROM AUTHOR]

The article offers information on the importance of project management in library and information science, noting its increasing recognition as a valuable skill for librarians. Topics include the adoption of project management principles in academic libraries, differences between libraries and businesses in project management practices, and challenges faced by libraries in implementing project management.

Implementation of agile technology and its effects on individuals, the environment, technology, and manufacturing factors are the focus of this study, with a special focus on agile technology's moderating effect. Consequently, this study investigates a unique conceptual framework to extend the notions of agile technology implementation to address this research gap. This conceptual framework has been subjected to empirical testing, with 380 population-representative employees serving as participants. This study establishes the inclusion requirements for Iraqi oil and gas (O&G) firms. Using a self-administered questionnaire, data are collected and analyzed using structural equation modeling partial least squares. The finding shows that there are various factors that have a positive effect on O&G companies in Iraq. The implementation of agile technology also has a partially significant positive moderating effect on these factors, indicating that agile technology can amplify the positive impact of these factors. This can lead to profits and the ability for companies to achieve long-term goals and a competitive advantage in the business environment while achieving sustainability in the O&G field. These findings are significant, as they suggest that the implementation of agile technology can have a positive impact on the O&G industry in Iraq, leading to long-term sustainability and profitability. [ABSTRACT FROM AUTHOR]

As part of agile methodologies seen in the past few years, IT organizations have continuously adopted new practices in their software delivery life-cycle to improve both efficiency and effectiveness of development teams. Two of these practices are continuous integration and continuous deployment, which are part of the DevOps cycle which has helped organizations build software effectively and efficiently. These practices must be considered for new technologies such as smart contracts, where security concerns and bugs might cost more once deployed than traditional software. This paper states the importance of using a proper DevOps routine and how it is possible to apply this practice to a smart contract build. Specifically, this paper introduces a framework to implement DevOps for smart contracts development by describing multiple DevOps tools and their applicability to smart contract development. [ABSTRACT FROM AUTHOR]

The market for electric bicycles has grown extremely and developed rapidly in recent years. To enter such a market with a new product, the development process has to be fast, and throughout the process, feedback from future potential customer(s) should be sought in order to achieve the best possible market acceptance. The article presents the design process of a pedelec e-bike central drive system. The authors were members of the development team and the designers of the mechanical transmission, and therefore had a good overview of the whole project. The development process and the set-up of production require a certain amount of time, during which design changes are inevitable due to changes in customer expectations and demands. The development team should respond to these changes and take them into account during development. Only the ability to react to changes and constant communication with the customer will ultimately lead to a product that can be commercially successful. Based on a critical review of the successfully completed project, general guidelines were established for the development of mechatronic products that consider the principles of Agile methodology. Particular attention was paid to the development of polymer gears, as these were the most demanding components in the system. The presented guidelines were based on an overview of the e-bike R&D process presented, but they can be generalized and used in the development process of any technical physical product. Agile methods were developed in the field of software development and therefore cannot be directly transferred to the field of physical product development. The article highlights and discusses individual special features that distinguish agile development of physical products from software development. [ABSTRACT FROM AUTHOR]

Aim/Purpose Using the Agile Adoption Framework (AAF), this study aims to examine the agile potential of software development companies in Nepal based on their agile maturity level. In addition, this study also examines the impact of various basic agile practices in determining the maturity level of the agile processes being implemented in the software industry of Nepal. Background Even if most organizations in the software sector utilize agile development strategies, it is essential to evaluate their performance. Nepal's software industry did not adopt agile techniques till 2014. The Nepalese industry must always adapt to new developments and discover ways to make software development more efficient and beneficial. The population of the study consists of 1,500 and 2,000 employees of software companies in Nepal implementing agile techniques. Methodology The sample size considered was 150 employees working in software companies in Nepal. However, only 106 respondents responded after three follow-ups. The sample was collected with purposive sampling. A questionnaire was developed to gain information on Customer Adaptive, Customer Collaboration, Continuous Delivery, Human Centric, and Technical Excellence related to agile practices along with the Agile Maturity Level. Contribution This research contributes to the understanding of agile practices adopted in software companies in developing countries like Nepal. It also reveals the determinants of the agility of software companies in developing countries. Findings The results suggest that some of the basic principles of agile have a very significant role in Agile Maturity Level in the Nepali context. In the context of Nepal, human-centered practices have a very high level of correlation, which plays a vital role as a major predictor of the agile maturity level. In addition, Technical Excellence is the variable that has the highest level of association with the Agile Maturity Level, making it the most significant predictor of this quality. Recommendations for Practitioners As Nepali software companies are mostly offshore or serve outsourcing companies, there is a very thin probability of Nepali developers being able to interact with actual clients and this might be one of the reasons for the Nepali industry not relying on Customer Adaptation and Collaboration as major factors of the Agile methodologies. Continuous Delivery, on the other hand, has a significant degree of correlation with Agile Maturity Level. Human-centric practices have a very high level of correlation as well as being a major predictor in determining the Agile Maturity Level in the context of Nepal. Technical Excellence is the most significant predictor and the variable which has the highest level of correlation with Agile Maturity Level. Practitioners should mainly focus on technical excellence as well as human-centric practices to achieve a higher level of Agile Maturity. Recommendations for Researchers There has not been any such research in the Nepali context that anyone could rely on, to deep dive into their organizational concerns regarding agile strategies and plans. Researchers will need to focus on a more statistical approach with data-driven solutions to the issues related to people and processes. Researchers will need to cover freelancers as well as academics to get a different perspective on what can be the better practices to achieve a higher level of agile maturity. Impact on Society This study on Agile work is accessible not only to the software industry but also to the general public. The Agile technique has had a huge impact on society's project management. It has revolutionized how teams approach project planning, development, and execution. The paper's findings will further information regarding the Agile methodology, which emphasizes collaboration and communication, fosters teamwork and higher quality work, and promotes the exchange of knowledge, ideas, and the pursuit of common goals. Future Research Owing to the limitations of this study, it is necessary to analyze agile practices in the Nepalese software sector using additional factors that influence agile maturity. The conclusion that years of agile experience do not serve as a balancing factor for both agile practices and the Agile Maturity Level requires additional research. Whether a software outsourcing firm or not, the organization type had no bearing on the degree of maturity of agile methods; this leaves space for further research. [ABSTRACT FROM AUTHOR]

Background: Software development teams are challenged with the adoption of the most appropriate software development methodology. Despite their acceptance of agile methodologies, still many countries use traditional software development methods. Objectives: The major objective of this study was to develop a contextualised model for the adoption of agile methodologies in software development teams in South Africa. Method: Our study identified the factors that contributed to the adoption of agile software development teams in South Africa by conducting a factor analysis. We used descriptive statistics to determine the frequencies of the participant's demographics and situational variables. A composite research model based on technology, organisation and environment, individual characters and culture constructs was constructed and analysis was performed by applying the statistical techniques of correlation analysis, regression analysis and structural equation modelling. Results: The result of the analysis revealed that many teams do not have a specific model that they use in agile development methodology. Technology, organisation, environment and culture constructs were found to have an impact on teams in adopting agile methodologies. Conclusion: The study demonstrated that organisations lack appropriate models of agile methodologies adoption to inform their decision making. Therefore, adopt the developed model in taking informed decisions for their software development methodologies. The study makes a practical contribution to management and practice. Contribution: This study improves on software development approaches in developing countries. The developed model can be adopted as a theory in future research. It contributed literature to the body of knowledge. [ABSTRACT FROM AUTHOR]

In software development, documentation is a continuous process that specifies what the system does, how it does it, and for whom it does it, describing all its characteristics from different perspectives in order to facilitate the understanding of all the interested parties. However, this is not always achieved due to poor documentation practices, leading to a type of technical debt known as documentation debt, which is related to missing, inconsistent, or incomplete documentation that degrades the understanding of the system, severely affecting its development, maintenance, and evolution. This phenomenon seems to be aggravated in agile approaches, either due to a misunderstanding of agile values and principles by focusing on the continuous delivery of functional software rather than comprehensive documentation, or a lack of good documentation practices. Although there are initiatives that generally describe the causes, effects, and good practices to mitigate documentation debt, it is still necessary to understand the impact of this type of debt on the software industry and to delve into a more complete definition in agile software development. In this sense, the results of a systematic mapping are presented, which provide a solid base of knowledge about documentation debt in agile software development and allow identifying gaps or research opportunities in this topic. [ABSTRACT FROM AUTHOR]

Experience shows that Agile project management tools such as Atlassian Jira capture the state of EAS projects by relying solely on expert judgement that is not supported by any knowledge model. Therefore, the assessment of project content against strategic objectives and business domain features are not supported by any tool. This is one of the reasons why Agile project management still does not provide sufficient EAS project delivery results. In order to address this problem, the Enterprise Application Software (EAS) development using Agile project management is summarized in a conceptual model. The model highlights the knowledge used and indicates its nature (empirical or causal digitized). The modified Agile management process we have developed and described in previous works is based on causal knowledge models that supports EAS development and Agile management processes. The purpose of this article is to specify knowledge repository to ensure the Agile management solutions of an EAS project are aligned with strategic goals and business domain causality. It is worth noticing that strategic goals have been identified and specified as capabilities using some enterprise architecture framework (NAF, MODAF, ArchiMate, etc.). The novelty of the proposed method is incorporating the business domain causal knowledge modelling approach into the Agile project management process. The causal knowledge unit is considered as a Management Transaction (MT), which includes closed loop dependence of its components. The modified Agile activity hierarchy (theme, initiative, epic, user story) defines the required content of their mutual interactions. An important new results obtained are the conceptual model of causal knowledge base (KB) and specification of enhanced Agile management tool components: project management database and project state assesment knowledge base. Causal KB includes specification of causal knowledge unit (MT metamodel) and specifications of traditional and causal Agile hierarchy meta-models. These conceptual models define the causal knowledge components necessary to evaluate the state of Agile activities in the EAS development project using intelligent Agile project management tool. [ABSTRACT FROM AUTHOR]

Context-- Making effort estimation as accurate and suitable for software development projects becomes a fundamental stage to favor its success, which is a difficult task, since the application of these techniques in constant changing agile development projects raises the need to evaluate different methods frequently. Objectives-- The objective of this study is to provide a state of the art on techniques of effort estimation in Agile Software Development (ASD), performance evaluation and the drawbacks that arise in its application. Methodology-- A systematic mapping was developed involving the creation of research questions to provide a layout of this study, analysis of related words for the implementation of a search query to obtain related studies, application of exclusion, inclusion, and quality criteria to filter nonrelated studies and finally the organization and extraction of the necessary information from each study. Results-- 25 studies were selected; the main findings are: the most applied estimation techniques in agile contexts are: Estimation of Story Points (SP) followed by Planning Poker (PP) and Expert Judgment (EJ). The most frequent solutions supported in computational techniques such as: Naive Bayes, Regression Algorithms and Hybrid System; also, the performance evaluation measures Mean Magnitude of Relative Error (MMRE), Prediction Assessment (PRED) and Mean Absolute Error (MAE) have been found to be the most commonly used. Additionally, parameters such as feasibility, experience, and the delivery of expert knowledge, as well as the constant particularity and lack of data in the process of creating models to be applied to a limited number of environments are the challenges that arise the most when estimating software in Agile Software Development (ASD). Conclusions-- It has been found there is an increase in the number of articles that address effort estimation in agile development, however, it becomes evident the need to improve the accuracy of the estimation by using estimation techniques supported in machine learning that have been shown to facilitate and improve the performance of this. [ABSTRACT FROM AUTHOR]

Agile methodologies are sometimes adopted, with the assumption that benefits can be attained by only using a set of best practices, which can sometimes work to a degree. In this paper, a case is discussed where a software‐producing organization of seven teams achieved significant improvements. The goal of the research was to answer two questions: how an already agile organization could improve its performance further and what is the impact of promoting quality aspects? The questions were answered by implementing interventions based on prior literature and data emerging from semi‐structured interviews. The context was an established business with a complex revenue stream structure, meaning the mix of various project/service/product based work rendered the adoption of agile methods a challenge. Action research comprising three rounds of interventions was conducted to improve the organization and its quality culture while enforcing code review practices. Interventions resulted in a significant improvement in quality, as measured by reported defects. Therefore, it is suggested that agile methods are not sufficient on their own to take software business forward unless a quality‐focused culture is simultaneously achieved through a mindset change and organizational structures to enforce quality practices. The paper contributes to research on the managerial practices of software business and agile transformation by providing empirical support to introducing formal quality improvement to the agile mix as a method for practitioners to improve organizations with complex business models and multiple teams. [ABSTRACT FROM AUTHOR]

Introduction. Several authors practice and disseminate good practices related to interactivity and agile, and from different areas and disciplines, as part of their activities, but few integrate them to develop projects. Objective. This paper presents the results of a review in which the level of dissemination of good practices related to these areas and those proposed for structuring, designing, and evaluating interactive content are investigated. Method. To conduct reliable literature reviews, it is necessary to build an initial protocol in which the research methodology is structured. Results. The final sample is made up of 100 works distributed mainly among articles, presentations at events, and online contributions. It was found that 47 % of the researchers publish about good practices to indicate an area or discipline of application, while 21 % describe them from interactivity and 24 % from agile. Conclusions. Furthermore, the good practices found are the result of personal experiences, not general validations, which makes it impossible to conclude whether they are really good. [ABSTRACT FROM AUTHOR]

Scrum is one of many agile frameworks and is considered the most popular and widely adopted. Although Scrum presents several advantages, process and final product quality continue to be Scrum's main challenges. The quality assessment should be an essential activity in the software development process. Several authors have attempted to improve the quality of Scrum projects, changing some aspects of the framework, such as including new quality practices, a quality role, and quality processes. However, the quantification of quality is still a challenge. For that reason, the authors proposed a framework called Scrumlity, which was defined in a previous study. This framework proposes a change to Scrum, including a quality role and some artifacts to evaluate quality through a complete execution of a Sprint. In this study, the authors add a User Story Quality assessment to the framework. The User Story Quality Assessment includes over 250 analyzed User Stories. Results obtained after this experiment indicate the importance of executing a User Story Quality Assessment and that Scrum Team members are willing to accept adding this to the framework. [ABSTRACT FROM AUTHOR]

Modern software development requires agile methods to deploy and scale increasingly demanded distributed systems. Practitioners have adopted the microservices architecture to cope with the challenges posed by modern software demands. However, the adoption and deployment of this architecture also creates technical and organizational challenges, potentially slowing down the development and operation teams, which require more time and effort to implement a quality deployment process that allows them to constantly release new features to production. The adoption of a DevOps culture, along with its practices and tools, alleviates some of these new challenges. In this paper we propose a guide for the deployment of systems with a microservices architecture, considering the practices of a DevOps culture, providing practitioners with a base path to start implementing the necessary platform for this architecture. We conducted this work following the Design Science Research Methodology for Information Systems (DSRM). In this way, we identified the problem, and also defined the solution objectives through the execution of a Systematic Literature Mapping and a Gray Literature Review, having as a result the proposed guide. This work can be summarized as follows: (I) Identification of practices and technologies that support the deployment of microservices. (II) Identification of recommendations, challenges, and best practices for the deployment process. (III) Modeling of the microservices deployment process using SPEM. (IV) Integration of the knowledge in a guide to deploying microservices by adopting DevOps practices. [ABSTRACT FROM AUTHOR]

Nowadays, power systems' Protection, Automation, and Control (PAC) functionalities are often deployed in different constrained devices (Intelligent Electronic Devices) following a coupled hardware/software design. However, with the increase in distributed energy resources, more customized controllers will be required. These devices have high operational and deployment costs with long development, testing, and complex upgrade cycles. Addressing these challenges requires that a 'revolution' in power system PAC design takes place. Decoupling from hardware-dependent implementations by virtualizing the functionalities facilitates the transition from a traditional power grid into a software-defined smart grid. This article presents a survey of recent literature on software-defined PAC for power systems, covering the concepts, main academic works, industrial proof of concepts, and the latest standardization efforts in this rising area. Finally, we summarize the expected future technical, industrial, and standardization challenges and open research problems. It was observed that software-defined PAC systems have a promising potential that can be leveraged for future PAC and smart grid developments. Moreover, standardizations in virtual IED software development and deployments, configuration tools, performance benchmarking, and compliance testing using a dynamic, agile approach assuring interoperability are critical enablers. [ABSTRACT FROM AUTHOR]

How can we make software services evolve safely and be long-lived? By designing on the premise of microservices, the services become loosely coupled, which can localise the changes in the system and accelerate the changes. However, from a medium- to long-term perspective, it is not easy to respond to changes in technology trends, business changes including legal revisions, and changes in user requirements among the changing project members. We propose DevFemOps as a way to enhance maintainability and achieve continuous quality improvement, coining the term DevFemOps to place Formal Engineering Methods at the center of the DevOps cycle. We also define the DevFemOps QA engineer as a new role within the agile development squad that is responsible for the quality of the product. In this paper, we will describe how the DevOps cycle, with QA engineers at the center, can bring us closer to the goal of DevFemOps. [ABSTRACT FROM AUTHOR]

Wireless network virtualization (WNV) is an evolving technology that supports networking for future wireless networks and agile IoT applications that optimize wireless bandwidth, provide network protection, and increase network performance in general. However, the exponential growth and increased demand for IoT have posed considerable scalability problems, interoperability, and heterogeneity across diverse fields from intelligent cities to healthcare, urban computing, and tactile fast internet growth. In this paper, IoT-based WNV (IoT-WNV) technology has been used. The leading technologies that create a scalable and stable network, consistent with many IoT products, for effective wireless virtualization in next-generation agile IoT systems are the networking function virtualization (NFV), mobile edge computing, and software-defined networks (SDNs). The network function virtualization (NFV) feature improves network stability, while the SDN operates, optimizes, and configures network services dynamically, enabling dynamically-based network functionality and interconnectivity. This special problem involves virtualizing IoT system wireless sensor networks to speed up network resource management by analyzing data obtained from devices deployed in various applications. This technological combination will satisfy the demands of modern applications. IoT-WNV aims to improve wireless virtualization for the next-generation network by implementing human-smart technology for load balance, network management, and network security. [ABSTRACT FROM AUTHOR]

This paper reports on Data Analytics Research (DAR), a course-based undergraduate research experience (CURE) in which undergraduate students conduct data analysis research on open real- world problems for industry, university, and community clients. We describe how DAR, offered by the Mathematical Sciences Department at Rensselaer Polytechnic Institute (RPI), is an essential part of an early low-barrier pipeline into data analytics studies and careers for diverse students. Students first take a foundational course, typically Introduction to Data Mathematics, that teaches linear algebra, data analytics, and R programming simultaneously using a project-based learning (PBL) approach. Then in DAR, students work in teams on open applied data analytics research problems provided by the clients. We describe the DAR organization which is inspired in part by agile software development practices. Students meet for coaching sessions with instructors multiple times a week and present to clients frequently. In a fully remote format during the pandemic, the students continued to be highly successful and engaged in COVID-19 research producing significant results as indicated by deployed online applications, refereed papers, and conference presentations. Formal evaluation shows that the pipeline of the single on-ramp course followed by DAR addressing real-world problems with societal benefits is highly effective at developing students' data analytics skills, advancing creative problem solvers who can work both independently and in teams, and attracting students to further studies and careers in data science. [ABSTRACT FROM AUTHOR]

The Brazilian General Data Protection Law (LGPD) implementation has impacted activities carried out by the software development teams. Due to it, developers had to become aware of the existing techniques and tools to carry out privacy requirements elicitation. Extending our previous work, we have investigated the actions taken by organizations regarding the LGPD, specifically in software development, considering the perception of agile development teams after two years of the LGPD implementation. In addition, we also investigated the perception of an agile team regarding the practices, techniques, and tools previously cited by practitioners as potential solutions for use in this context, along with techniques already in use in the current context. We have conducted a systematic literature review (SLR) and selected 36 primary studies. Furthermore, we have conducted a survey with 53 IT practitioners and semi-structured interviews with ten practitioners. The LGPD principles are known by most agile teams and are being implemented by the organizations, although the existing tools to support privacy requirements elicitation are still underused by agile teams. Moreover, agile teams consider that software requirements and software construction are the most impacted areas of knowledge by the LGPD, and most of them use user stories in privacy requirements elicitation. Our findings reveal that agile teams and Brazilian organizations are more concerned with user data privacy issues after the LGPD became effective. However, agile teams still face challenges in privacy requirements elicitation. [ABSTRACT FROM AUTHOR]

The nine papers in this special section focus on new developments in agile software and reports on applications for its use. A key aspect for the extensive use of agile software is that it supports developers with coping with the growing uncertainty and turbulence in technological and market environments. Feedback and change are at the core of Agile for a dynamic, evolving, and organic, rather than static, predefined, and mechanistic development process advocated by waterfall management. To create timely, high-quality, cost-efficient, and innovative solutions, Agile developers organized in small, colocated, autonomous teams, build and test software in rapid iterative cycles, actively involving users to gather feedback, updating the project scope, and plan "on-the-fly," using face-to-face communication as opposed to documentation. These papers contribute to the state-of-the-art of agile research by offering a rich, up-todate account of the dynamics occurring when expanding Agile into "not-just-software" contexts of the key challenges and perils related to the scaling and of the possible solutions to them. [ABSTRACT FROM AUTHOR]

As software products increasingly become part of larger ecosystems, research and development (R&D) units of software producers organize themselves around projects to become more responsive to the environment. Organizations participating in software ecosystems must continuously adapt and adjust their software development and maintenance processes to drive both medium-term and long-term innovation. Agile methods and practices are widely adopted to guide the collaboration within and between project teams in software development. Moreover, when successfully attained, agility can drive innovation by enabling software development organizations to cope with technological changes and exploit emerging opportunities in software ecosystems. In this article, we focus on how organizations attain agility in the maintenance and development of software products. To answer this question, we conduct a longitudinal case study of Agile Scrum implementation in the R&D unit of a major supplier of telecommunication equipment. We investigate the emerging tensions and highlight practices used to balance these tensions in the Agile Scrum implementation. We identify four capabilities and ten practices that support effective collaboration and coordination in the development and maintenance of software products. The study offers practical guidance for R&D managers to attain agility in software ecosystems. [ABSTRACT FROM AUTHOR]

In order to increase the ability to build complex, software-intensive systems, as well as to decrease time-to-market for new functionality, automotive companies aim to scale agile methods beyond individual teams. This is challenging, given the specifics of automotive systems that are often safety-critical and consist of software, hardware, and mechanical components. In this article, we investigate the concrete reasons for scaling agility beyond teams, the strategies that support such scaling, and the foreseeable implications that such a drastic organizational change will entail. The investigation is based on a qualitative case study, with data from 20 semistructured interviews with managers and technical experts at two automotive companies. At the core of our findings are observations about establishing an agile vehicle-level feedback loop beyond individual teams. First, we find that automotive original equipment manufacturers aim to decrease the lead time of development. Second, we also identify seven strategies that aim to enable scaled-agile beyond teams. Finally, we extract six foreseeable implications and side effects of scaling agile beyond teams in automotive. By charting the landscape of expected benefits, strategies, and implications of scaling agile beyond teams in automotive, we enable further research and process improvements. [ABSTRACT FROM AUTHOR]

Dealing with an uncertain and dynamic environment when facing multiple and fast-paced challenges forces professionals to adopt agile practices in different environments, resulting in the use of hybrid project management models. However, identifying the right practice to adopt can be challenging, given the variety of project types and environmental factors. In this article, a recommendation method that would allow for the identification of patterns of project management practices for different environments—using an agility indicator—is proposed. The proposed method is tested with a dataset of 856 projects. A cluster analysis is applied to divide the projects into three groups according to environmental characteristics, called scenarios: waterfall, agile, and hybrid. Then, we apply the association rule technique for each group separately, identifying specific patterns of practice for each group. Through a comparative analysis, we verify the consistency between the recommendations of the proposed method for each scenario and the literature on project management. The results indicate the feasibility of the proposed method, thus opening up new research opportunities for hybrid models that can be customized for different projects. This article can help project management professionals apply the agile method beyond its use in software development and improve the process of combining project management practices. We also suggest directions for new research to advance the knowledge of useful decision support tools for hybrid model customization. [ABSTRACT FROM AUTHOR]

The cultural component of the project team is recognized as one of the most critical factors in the implementation of agile project management (APM), especially in nonsoftware industries, where the diffusion of APM still involves several challenges. Particularly, the successful implementation of scrum—the most diffused APM methodology—seems related to the project teams’ subculture, which may differ from the overall organizational culture of the company. This article contributes to the APM literature in nonsoftware contexts by studying the cultural values that develop inside agile teams and the scrum principles and practices that are particularly relevant for fostering these values. Using interview data collected from seven manufacturing and service organizations, we use the competing value framework as the theoretical model to understand the cultural profiles of their organizations, how they deploy into the project teams’ subculture, and what, if any, connections exist with the adoption of scrum principles and practices. We find that clan and market values are the dominant subcultures in agile teams. These cultural values are fostered at a strategic level by a subset of scrum values (i.e., courage, openness, and respect) and pillars (i.e., transparency and adaptation). At an operational level, retrospective meetings and the definition of particular artifacts also contribute to develop these dominant cultural values. [ABSTRACT FROM AUTHOR]

Agile practices present one approach for firms to adapt to an increasingly dynamic and competitive environment. Although prior studies have investigated performance outcomes of agile projects, agile practices’ consequences on a project team's collaborative processes have not yet been thoroughly analyzed. It also remains unclear whether practices on a higher organizational level, such as project portfolio management (PPM), support or constrain agile practices’ benefits, especially if a firm simultaneously conducts traditionally managed and agile projects. Therefore, this article investigates the role of agile practices for a project's teamwork quality (TWQ) and project success and examines the influence of organizational contingencies. Specifically, we conceptually and empirically analyze the moderating impact of PPM practices on the relationship between agile practices, TWQ, and project success. A multi-informant analysis of 378 projects nested in 100 portfolios shows that agile practices positively relate to project success through TWQ. We find that traditional PPM practices such as business case existence, strategic clarity, and operational control constrain this relationship. Our article contributes to the literature on project teams and portfolio management by providing empirical insights on the interaction between project and portfolio management practices. [ABSTRACT FROM AUTHOR]

Since 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. [ABSTRACT FROM AUTHOR]

Many modern radars use variable pulse repetition intervals (PRI) to improve anti-reconnaissance and anti-jamming performance. Their PRI features are probably software-defined, but the PRI values at different time instants are variable. Previous statistical pattern analyzing methods are unable to extract such undetermined PRI values and features, which greatly increases the difficulty of Electronic Support Measures (ESM) against such radars. In this communication, we first establish a model to describe the temporal patterns of software-defined radar pulse trains, then introduce the recurrent neural network (RNN) to mine high-order relationships between successive pulses, and finally exploit the temporal features to predict the time of arrival of upcoming pulses. In the simulation part, we compare different time series prediction models to verify the RNN's adaptability for pulse sequences of variable parameter radars. Moreover, behaviors of different RNN units in this task are compared, and the results show that the proposed method can learn complex PRI features in pulse trains even in the presence of significant data noises and agile PRIs. [ABSTRACT FROM AUTHOR]

In the traditional radar emitter recognition task, the number of emitter category tags is fixed and relatively small. We input the pulse characteristic parameters into the machine learning model to model the radar emitter. The radar emitters with agile waveform involves four different waveform categories. The number of specific emitter categories contained in different waveform categories is extremely unbalanced. Their parameters vary widely, so only using the same model or strategy to model each waveform category cannot effectively extract the core features of the radar emitters with agile waveform. The above is the main reason for the low recognition accuracy of the recognition task of radar emitters with agile waveform. In this paper, a deep reinforcement learning framework is designed to be used in the intelligent recognition task of radar emitters with agile waveform. The task is regarded as a two‐step decision game. We use CNN and Bi‐LSTM to model the radar emitter, and calculate the initial state and transition state of the game. At the same time, we design the penalty function in reinforcement learning and increase the penalty for the wrong decision in the first step to deal with the imbalance of the number of emitters between different waveform categories. Finally, the Q‐Learning algorithm with approximate values is used to learn the control strategy of the game, that is, the modeling and recognition strategy adopted for emitters of different waveform categories. The simulation experiment results show that the deep reinforcement learning framework constructed in the article can improve the recognition accuracy of 1.2% compared with the state‐of‐the‐art method in the intelligent recognition task of radar emitters with agile waveform. [ABSTRACT FROM AUTHOR]

The competition in the software market demands that the time required for any software product to reach the market be reduced if the product is to survive competition from other developers. The pursuit of this goal has led to the adoption of agile software development methodologies. While other agile methodologies provide guidelines as to the software engineering (SE) practices to be used during the development lifecycle, Scrum does not. The purpose of this study is twofold: first, to identify the usage and level of importance of software engineering practices in the Scrum development environment; and second, to investigate how Scrum teams adopt an appropriate set of SE techniques and whether a hybrid Scrum/Extreme Programming (XP) methodology is an appropriate approach to take. This research was conducted by examining sample data from five organizations using the Scrum methodology. The sample included a range of industries including communications and embedded systems, financial asset management, software development houses and consulting firms in South Africa. The study employed a mixed method approach. A key finding was that, regardless of the fact that Scrum does not explicitly recommend engineering practices, there was extensive use of these practices by all of the participating organizations. The study also found that the lack of software engineering practices in Scrum does not constitute a barrier to a successful adoption of Scrum, provided the 'inspect and adapt' principle inherent in Scrum is properly followed. The study discusses the findings, explains the implications and suggests future research. [ABSTRACT FROM AUTHOR]

Microbiology research is one of the research fields that deal with a huge volume of microbial culture collection data which needs to be preserved, due to its importance as a key resource center for obtaining, identifying, producing, preserving, cataloging, and distributing culture data of various microbes. Currently, the collection and storing of microbial culture data is performed manually via various data transfers into record books, logbooks, or spreadsheets. However, the manual process seems to be impractical as it is highly prone to human error and time-consuming, aside from the struggle of managing and retrieving the data. Therefore, to address this issue, we have successfully designed and developed a customized database for microbial data collection that allows users to store, access, visualize and retrieve information in a single platform. The agile development approach has been implemented during the software development process allowing more flexibility during the development phase yet managing to fulfill the functional requirements of the end-users. The front end is created using the Bootstrap framework, an open-source and powerful platform for developing user-friendly web pages and web applications. It is connected to the back-end MySQL database as a relational database management system to organize structured data. As a result, the developed microbial culture collection has eliminated manual data entry and accelerated the data retrieval process. The platform is a one-stop platform for microbiologists when dealing with microbial culture collection data. [ABSTRACT FROM AUTHOR]

Agile Software Development Methods support an iterative and incremental way of developing software systems while responding to change by prioritising various aspects at different times. This differs from traditional sequential methods like Waterfall, in which one software development stage has to be completed before starting the next stage. To produce software systems that meet the requirements of their institutions, several governments in Africa have issued standards and guidelines to be followed during the development of government software systems. Such standards and guidelines specify the specific activities and deliverables for each stage of software development. While well-intentioned, such guidelines and standards can also hinder creativity and innovation which could be key to producing good quality and sustainable software systems. Given the degree of leniency that they offer, Agile methods could give room for such creativity and innovation among team members. However, despite such good potential in Agile methods, the literature lacks evidence regarding if and how the software development guidelines and standards issued by several African governments support agility. Various documents from three East African countries were reviewed, to determine if and how they support for agility during the development of government software systems. Guidelines and standards were reviewed using the lens of four Agile Values stated in the Agile manifesto. Results show the following: there is a marked lack of support for agility during the development of government software systems; the standards and guidelines are generally characterised by excessive micromanagement of the development process, leaving little or no room for innovation and creativity amongst members of the development teams; and the guidelines seem to assume uniformity across development projects, irrespective of the fact that software development projects can vary depending specific contextual dictates. Furthermore, recommendations on how governments can adopt and support agility during software development are provided. [ABSTRACT FROM AUTHOR]

DevOps has become an important set of organisational and technical practices in software development under the agile umbrella. Many efforts are still being made in this field, mainly focused on the inclusion of metrics for monitoring progress. Gathering metrics is a difficult task, but it can provide insight into the performance of the software delivery process. The current status of the definition, application and implementation of metrics in DevOps projects and processes is of interest to software practitioners. Thus, the objective of this article is to analyze documents regarding the impact of metrics in DevOps projects. 103 documents were obtained from the Scopus database to analyze them through the bibliometric method considering several aspects. The bibliometric analysis performed included author analysis, author affiliation, authors’ countries, keyword analysis, citation analysis, and network analysis. The results indicate that DevOps research is not centralized in a specific group of researchers. Moreover, the most significant contributions of DevOps are related to continuous integration, software design, and software testing. The bibliometric analysis presented in this article helps to identify the current state of the DevOps literature and provides an insightful discussion of future research trends. [ABSTRACT FROM AUTHOR]

Due to their expanded methods, agile methodologies are now the accepted standard for software development. Collaboration, addressing changing requirements with workable software, and simple design are just a few aspects of typical techniques. By employing the aforementioned approaches, these methods handle the issue of variable requirements. As a result, these methods lower the cost of changes at a later point in the software development process. Due to the unpredictability of requirements, such methodologies do not hold up well for an early estimate of size, cost, and timeframe. Agile techniques, it has been noticed, rely on expert analysis and prior project information to estimate cost, complexity, and time. Such approaches, it has been discovered, do not take into account the critical aspects affecting the project's cost, complexity, and timeframe when estimating. Based on predefined estimation methods including analogy and planning, poker becomes unexpected in the lack of historical data and professionals. As a result, there is a pressing need to develop a simple computational solution that takes into account the factors that influence the project budget, complexity, and timeframe. It also serves as a foundation for unskilled practitioners to make better estimates. The research of both traditional and agile estimation techniques with a comparability of concepts and variations is presented in this work. We looked into a few key elements that influence the estimation of an agile project with lower, moderate, and higher scalability factors. Integrating critical aspects is also recommended using the Constructive Agile Estimation Algorithm (CAEA). [ABSTRACT FROM AUTHOR]