Search

One of the significant challenges in scaling agile software development is organizing software development teams to ensure effective communication among members while equipping them with the capabilities to deliver business value independently. A formal approach to address this challenge involves modeling it as an optimization problem: given a professional staff, how can they be organized to optimize the number of communication channels, considering both intra-team and inter-team channels? In this article, we propose applying a set of bio-inspired algorithms to solve this problem. We introduce an enhancement that incorporates ensemble learning into the resolution process to achieve nearly optimal results. Ensemble learning integrates multiple machine-learning strategies with diverse characteristics to boost optimizer performance. Furthermore, the studied metaheuristics offer an excellent opportunity to explore their linear convergence, contingent on the exploration and exploitation phases. The results produce more precise definitions for team sizes, aligning with industry standards. Our approach demonstrates superior performance compared to the traditional versions of these algorithms. [ABSTRACT FROM AUTHOR]

Software Development based on Scrum Agile in a distributed development environment plays a pivotal role in the contemporary software industry by facilitating software development across geographic boundaries. However, in the past different frameworks utilized to address the challenges like communication and collaboration in scrum agile distributed software development (SADSD) were notably inadequate in transparency, security, traceability, geographically dispersed location work agreements, geographically dispersed teamwork effectiveness, and trust. These deficiencies frequently resulted in delays in software development and deployment, customer dissatisfaction, canceled agreements, project failures, and disputes over payments between customers and development teams. To address these challenges of SADSD, this paper proposes a new framework called ChainAgile, which leverages blockchain technology. ChainAgile employs a private Ethereum blockchain to facilitate the execution of smart contracts. These smart contracts cover a range of functions, including acceptance testing, secure payments, requirement verification, task prioritization, sprint backlog, user story design and development and payments with the automated distribution of payments via digital wallets to development teams. Moreover, in the ChainAgile framework, smart contracts also play a pivotal role in automatically imposing penalties on customers for making late payments or for no payments and penalties on developers for completing the tasks that exceed their deadlines. Furthermore, ChainAgile effectively addresses the scalability limitations intrinsic in blockchain technology by incorporating the Interplanetary File System (IPFS) is used for storage solutions as an off-chain mechanism. The experimental results conclusively show that this innovative approach substantially improves transparency, traceability, coordination, communication, security, and trust for both customers and developers engaged in scrum agile distributed software development (SADSD). [ABSTRACT FROM AUTHOR]

Self-supervised learning (SSL) is a potential deep learning (DL) technique that uses massive volumes of unlabeled data to train neural networks. SSL techniques have evolved in response to the poor classification performance of conventional and even modern machine learning (ML) and DL models of enormous unlabeled data produced periodically in different disciplines. However, the literature does not fully address SSL's practicalities and workabilities necessary for industrial engineering and medicine. Accordingly, this thorough review is administered to identify these prominent possibilities for prediction, focusing on industrial and medical fields. This extensive survey, with its pivotal outcomes, could support industrial engineers and medical personnel in efficiently predicting machinery faults and patients' ailments without referring to traditional numerical models that require massive computational budgets, time, storage, and effort for data annotation. Additionally, the review's numerous addressed ideas could encourage industry and healthcare actors to take SSL principles into an agile application to achieve precise maintenance prognostics and illness diagnosis with remarkable levels of accuracy and feasibility, simulating functional human thinking and cognition without compromising prediction efficacy. [ABSTRACT FROM AUTHOR]

Many organizations have adopted agile values and principles in their products and services to provide increasing value to their customers. Although agile started with software development, it has been applicable and used in different industries and disciplines, including the space industry. This article presents the practical implications of teams transitioning to be agile teams using a general inductive analysis of 33 individuals from different NASA agile teams. The findings and recommendations are part of a larger effort performed as part of the development of a model for agile leadership. Some organizations may see agile as very risky and costly, and this article provides some guidance derived from the data to help support planning for agile transformation efforts. • Agile transformations of NASA Agile teams. • Being Agile with a continuous learning mindset. • Ability to create sustainable value to the customer in a technology-driven organization. • Recommendations to becoming Agile organizations. [ABSTRACT FROM AUTHOR]

Digital transformation in the public sector provides digital services to the citizens aiming at increasing their quality of life, as well as the transparency and accountability of a public administration. Since adaptation to the citizens changing needs is central for its success, Agile methodologies seem best suited for the software development of digital services in that area. However, as well documented by an attempt to use Scrum for an important Public Administration in Italy, substantial modifications to standard Agile were needed, giving rise to a new proposal called improved Agile (in short, iAgile). Another notable example is the Scrum@IMI method developed by the City of Barcelona for the deployment of its digital services. However, given the importance of digital transformation in the public sector and the scarcity of efforts (documented in the scholarly literature) to effectively bring Agile within it, a strategically important contribution that Computer Science can offer is a general paradigm describing how to tailor Agile methodologies and, in particular, Scrum, for such a specific context. Our proposal, called Scrum@PA, addresses this strategic need. Based on it, a public administration has a technically sound avenue to follow to adopt Scrum rather than a generic set of guidelines as in the current state of the art. We show the validity of our proposal by describing how the quite successful Scrum@IMI approach can be derived from Scrum@PA. Although iAgile can also be derived from our paradigm, we have chosen Scrum@IMI as a pilot example since it is publicly available on GitHub. [ABSTRACT FROM AUTHOR]

Although there have been some studies on the success factors for IT software projects, there is still a lack of coherent research on the success factors for IT service projects. Therefore, this study aimed to identify and understand the factors and their relationships that contribute to the success of IT service projects. For this purpose, multivariate regressions and structural equation models (SEMs) were developed and analyzed. The regression models included six project management success criteria used as dependent variables (quality of the delivered product, scope realization and requirements, timeliness of delivery, delivery within budget, customer satisfaction, and provider satisfaction) and four independent variables (agile techniques and change management, organization and people, stakeholders and risk analysis, work environment), which had been identified through exploratory factor analysis. The results showed that not all success factors were relevant to all success criteria, and there were differences in their importance. An additional series of exploratory and confirmatory factor analyses along with appropriate statistical measures were employed to evaluate the quality of these four factors. The SEM approach was based on five latent constructs with a total of twenty components. The study suggests that investing in improving people's knowledge and skills, using agile methodologies, creating a supportive work environment, and involving stakeholders in regular risk analysis are important for project management success. The results also suggest that the success factors for IT service projects depend on both traditional and agile approaches. The study extensively compared its findings with similar research and discussed common issues and differences in both the model structures and methodologies applied. The investigation utilized mathematical methods and techniques that are not commonly applied in the field of project management success modeling. The comprehensive methodology that was applied may be helpful to other researchers who are interested in this topic. [ABSTRACT FROM AUTHOR]

The present trend of automation and digitization of jobs has made the skills gap even more pronounced, indicating that graduates are not sufficiently prepared for the challenges they will face in their careers. The educational process needs to adapt quickly to the demands made by employers and the job market. Learning tasks, assignments, and activities should mimic the practice environment as far as possible, to best prepare students for practice. One of the best approaches appears to be the incorporation of agile project management techniques and project-based learning into the educational process. The primary aim of this research is to examine the effects of implementing agile management techniques and project-based learning into education on students' skill sets and performance improvement rates. The activities and results that the students produced throughout the semester were gathered and assessed over two academic years. The course feedback was also gathered to investigate students' opinions about the course and their involvement during the semester. An exploratory study was conducted in order to achieve the results. The influence of implemented innovations on the course was addressed, and the acquired outcomes were contrasted and appraised. [ABSTRACT FROM AUTHOR]

The design-building of IT services in data centers has been historically conducted by applying rigorous IT service design-building phases-workflows. Consequently, relevant research has been conducted upon these rigorous phases-workflows to provide theoretical foundations and practical guidance to IT service design-building architects. However, the current dynamic business-governmental environment is demanding agile approaches, and research from this perspective is still very scarce. This research, thus, aims to provide an updated review and quantitative evaluation of the main rigorous (ITIL v2011, CMMI-SVC v1.3, and ISO/IEC 20000-1:2018) and main agile (ITIL v4, VeriSM, and ISO/IEC 29110-4-3) IT service design-building phases-workflows. For this aim, we conduct a conceptual review research methodology enhanced with an analytics hierarchical process (AHP) method to assess quantitatively how well these six IT service design-building phases-workflows fit two theoretical expected rigorous and agile IT service design-building phases-workflows pro formas. We found that the ITIL v2011 and CMMI-SVC v1.3 phases-workflows fit the rigorous pro forma with a high level, and the ISO/IEC 20000-1:2018 fits a moderate level, whereas all these three ones fit a low level the agile pro forma, as it was expected. ITIL v4 and VeriSM were found to fit a high level the agile pro forma but the ISO/IEC 29110-4-3 fits a moderate level. Unexpectedly, ITIL v4 and the ISO/IEC 29110-4-3 fit a moderate and moderate levels the rigorous pro forma, but VeriSM fits a low level as it was expected. Hence, we can conclude that ITIL v4 and VeriSM provide the most agile IT service design-building phase-workflow, and CMMI-SVC v1.3 the most rigorous one. The ISO/IEC 20000-1:2018 and ISO/IEC 29110-4-3 standards are still aligned to the rigorous approach, and ITIL v4 exhibits a dual moderate rigorous and high agile profile. Hence, this research provides ITSM professionals with an updated analysis useful to guide the selection and application of the IT service design-building phase-workflow—rigorous or agile one—in data centers. This research also contributes to the IT service design-building literature with updated insights and proposes specific research avenues to advance our scientific knowledge on how to design-building IT services. [ABSTRACT FROM AUTHOR]

Lithium-ion cells (LIC) are emerging as the critical energy source in space applications for spacecraft. The analysis of the failure of small satellites reveals that 41.3% have either suffered partial or total failures in the space environment around Earth, resulting in the accumulation of debris. The defects in batteries caused more failures than thrusters. The present paper details a framework for ensuring the durability of LIC systems in space applications. It is discussed in three verticals viz. a) Durability through Design' that gives prominence to best practices in cell chemistry selection, processing and, design through parametric modelling; b) 'Durability through quality control and testing by the manufacturer and by identifying relevant reliability models; c)'On-orbit management' through the State of Health (SOH) assessment by Random Forest algorithm and a well-equipped intelligent Battery Management System (BMS). Lacuna in standards for cell development process is brought out. Importance of quantitative approach for design, reliability and asset management during space application is highlighted. Use of agile, contemporary techniques of artificial intelligence in this quantitative approach is also discussed. The framework tries to bring out a systematized protocol to be followed during the development and operational life cycle of LIC for ensuring highly reliable systems for space application. [ABSTRACT FROM AUTHOR]

The major challenge of most basic schools is inadequate educational resources despite a conscious effort to constantly provide. This is a result of inaccurate data management leading to inappropriate predictions for effective planning. The actual efficiency of a system is determined by its ability to predict real-life data with speed and accuracy. In this work, the neural educational expert system (ES) is evaluated using mathematical models for predicting the availability of resources for the growing school-aged population using a criteria-based formative evaluation to know resource life and its effect on availability. This will help in the decision to add more resources by knowing when and how the resources should be added. Technical mathematical model generation through differential equations is used to fuse the factors affecting the availability of educational resources. The real-life data is used in prediction regarding the actual enrollment of learners and the availability of resources. The model is evaluated and critically analyzed to know the degree of accuracy and the steady state. The findings revealed that the resources decay and attrite at an exponential rate in the long run and the constant number of resources provided cannot cater for the rate of decay, resulting in inadequacy. A proposed algorithm for managing the resources is presented. Plain Language Summary: Purpose: The main aim of this work is to evaluate the agile neural educational system and find out the reasons behind the inadequate resources despite the effort to make resources adequate in schools. methods: methodology adopted is criteria-based formative evaluation using differential equations with initial value problem. conclusions: Inadequate educational resources affect the process of learning. Poor performance at the foundation affects higher levels of learning. Careful planning, provision, and management of educational resources can best be achieved by using the model to monitor the availability and provision of resources. This can be done through the careful control of two major factors; the addition of resources at regular intervals and good maintenance skills to reduce the decay of resources. This will minimize the cost of education which usually forms a major component of the budgets in countries. Going forward, it is prudent for the country to adopt this model to manage educational resources. implications: stakeholders of education will minimize the cost of education which usually forms a major component of the budgets in countries. Going forward, it is prudent for the country to adopt this model to manage educational resources. Limitations: this work is limited to resources in the form of physical quantities at the basic level of education. [ABSTRACT FROM AUTHOR]

The systematic design, building and implementation of IT services for on-premise, cloud-based or hybrid data centers are a hard engineering and managerial process. Heavyweight IT service design workflows—from ITIL v2011, CMMI-SVC v1.3 and the ISO/IEC 20000 standard—have been used in the last decade. However, the current dynamic business requirements demand to accelerate IT service design, building and implementation. Consequently, agile workflows—from ITIL v4 and VeriSM—or lightweight ones—from ISO/IEC 29110-4-3 standard and FitSM—have been proposed. However, despite these IT service design workflows provide high valuable content, they are still reported in a coarse-grain level, and thus academics and practitioners interested in using to them must add ad-hoc roles, activities-tasks, and artifacts-templates. In this research, we address this relevant knowledge gap, and using a Design Science Research Methodology (DSRM), we elaborate and evaluate exploratory an agile IT service design workflow—called AVS_FD_MVITS—that provides fine-grain content regarding roles, activities-tasks and artifacts-templates. AVS_FD_MVITS was designed using design components taken from Scrum-XP and ITIL v4 IT service design workflows. To evaluate exploratory AVS_FD_MVITS, we applied it in a realistic case in an academic small data center. The exploratory qualitative-based evaluation suggests that AVS_FD_MVITS can be considered a valid agile IT service design workflow useful for academics and practitioners. However, confirmatory quantitative-based evaluations are asked for advancing this research stream. [ABSTRACT FROM AUTHOR]

Background: Appropriate use of available inpatient beds is an ongoing challenge for US hospitals. Historical capacity goals of 80% to 85% may no longer serve the intended purpose of maximizing the resources of space, staff, and equipment. Numerous variables affect the input, throughput, and output of a hospital. Some of these variables include patient demand, regulatory requirements, coordination of patient flow between various systems, coordination of processes such as bed management and patient transfers, and the diversity of departments (both inpatient and outpatient) in an organization. Methods: Mayo Clinic Health System in the Southwest Minnesota region of the US, a community-based hospital system primarily serving patients in rural southwestern Minnesota and part of Iowa, consists of 2 postacute care and 3 critical access hospitals. Our inpatient bed usage rates had exceeded 85%, and patient transfers from the region to other hospitals in the state (including Mayo Clinic in Rochester, Minnesota) had increased. To address these quality gaps, we used a blend of Agile project management methodology, rapid Plan-Do-Study-Act cycles, and a proactive approach to patient placement in the medical-surgical units as a quality improvement initiative. Results: During 2 trial periods of the initiative, the main hub hospital (Mayo Clinic Health System hospital in Mankato) and other hospitals in the region increased inpatient bed usage while reducing total out-of-region transfers. Conclusion: Our novel approach to proactively managing bed capacity in the hospital allowed the region's only tertiary medical center to increase capacity for more complex and acute cases by optimizing the use of historically underused partner hospital beds. [ABSTRACT FROM AUTHOR]

This study presents the design and implementation of a high-resolution radar extended target simulation system for simulating extended target echoes in high-resolution radar. The study establishes target echo models for one-dimensional distance targets, two-dimensional surface targets, and three-dimensional volume targets. The key technologies used to achieve the design and implementation of the high-resolution radar extended target simulation system include wideband RF receiver technology, large instantaneous bandwidth baseband echo signal generation technology, target RCS(Radar Cross Section) data acquisition and modulation technology, and wideband agile frequency synthesizer. The system is used to conduct RF simulation and two-dimensional imaging processing of a typical fighter jet target, and the results are compared with the simulation results obtained using RadBase simulation software to verify the effectiveness of the system. The validation results indicate that the RF simulation and two-dimensional imaging processing results of the system are consistent with the simulation results obtained using the RadBase software. [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]

Software Size Measurement is a critical task in Software Development Life Cycle (SDLC). It is the primary input for effort estimation models and an important measure for project control and process improvement. There exist various size measurement methods whose successes have already been proven for traditional software architectures and application domains. Being one of them, functional size measurement (FSM) attracts specific attention due to its applicability at the early phases of SDLC. Although FSM methods were successful on the data-base centric, transaction oriented stand-alone applications, in contemporary software development projects, Agile methods are highly used, and a centralized database and a relational approach are not used as before while the requirements suffer from a lack of detail. Today's software is frequently service based, highly distributed, message-driven, scalable and has unprecedented levels of availability. In the new era, event-driven architectures are appearing as one of the emerging approaches where the 'event' concept largely replaces the 'data' concept. Considering the important place of events in contemporary architectures, we focused on approaching the software size measurement problem from the event-driven perspective. This situation guided us to explore how useful event as a size measure in comparison to data-movement based methods. The findings of our study indicates that events can be promising for measurement and should be investigated further in detail to be formalized for creating a measurement model thereby providing a replicable approach. [ABSTRACT FROM AUTHOR]

Agile approaches being practised by multiple teams operating remotely are widely adopted for large software development efforts these days. An agile setting is typically characterized by flexibility, to accommodate changing customer demands for continuous delivery of business value. A distributed setting brings about multiple demands for stability, in terms of a push for clear specification of requirements and design, and a big picture product definition. Therefore, implementing agile distributed development (ADD) projects results in an inherent conflict that must be reconciled. This article attempts to provide nuanced clarity on the notion of conflict between flexibility and stability and its management across variants of an ADD setup. Through multiple case studies, our findings suggest that the specific mode of agile project engagement and distributed team configuration drives the response to flexibility and stability respectively. Leveraging ambidexterity as a theoretical lens, this study contributes to the literature by providing insights beyond the earlier conceptualization of flexibility-stability conflict for the ADD setting. It considers contextual elements to understand the dynamics of conflicting forces. An empirical contribution of this research is the managerial framework that should assist practice in future implementations. [ABSTRACT FROM AUTHOR]

In today's fast-paced business environment, implementing strategies through programs, projects, and business-as-usual activities can be challenging for companies. The telecommunication industry, in particular, faces these challenges as it experiences the effects of digital transformation and fast-changing markets. It requires a flexible and adaptive approach to project portfolio management (PPM) to optimize investments and deliver value. This article presents a successful case study of a PPM process using the Stage-Gate model in a prominent telecommunications company that operates in a dynamic and fast-growing environment. The Stage-Gate PPM model comprises four stages: Proposal Selection, Selection of Nominated Demands, Prioritization, and Categorization of Projects. The model is unique as it can be adapted to different projects and incorporates elements of Agile approaches, such as Portfolio Sprint meetings and artefacts. The study demonstrates the importance of a well-defined PPM process in coordinating short-term and long-term activities and effectively allocating time, money, and resources. The Stage-Gate PPM model can potentially enhance project success rates and bring greater value to companies by ensuring the realization of suitable projects. This article contributes significantly to the existing literature on portfolio management, providing valuable insights and lessons applicable to other companies in the industry to enhance their portfolio management processes. Furthermore, this study can interest scholars and researchers seeking to explore effective portfolio management in other complex and dynamic environments. [ABSTRACT FROM AUTHOR]

In the last years a type of financial institution has emerged, named fintechs, with reduced capital structure, no physical bank agencies and offering more agile functionalities, without the majority of fees and the typical bureaucracy of the traditional banks. In order to extend the credit offers possibilities, the Brazilian Economic and Social Development Bank (BNDES) sought the fintechs as partners, causing the Bank to adapt to a more agile business model. Such a process was characterized as an organizational culture change put into practice through its digital transformation. At the same time, the world has been impacted by the COVID-19 pandemic, which was a trigger to accelerate the process. This article presents a case study that describes the adaptation process of BNDES to the agile methodology of the fintechs, during the period of 2019 to 2021, as a vector of the bank's digital transformation. The results of this article aligned the main topics of the case study to the theoretical references, thus allowing the identification of the convergence points between theory and practice. Amongst the main results, one highlights the effort made to disseminate the agile methodology by forming multidisciplinary squads with the delivery of incremental minimum viable products, the integration of data bases and systems for real time collaboration, and the importance of the senior management to sponsor BNDES successful digital transformation process. [ABSTRACT FROM AUTHOR]

The cost-reducing potential of intelligent supply chains (ISCs) has been recognized by companies and researchers. This paper investigates a two-echelon steel supply chain scheduling problem that considers the parallel-batching processing and deterioration effect in the production stage and sufficient vehicles in the port delivery stage. To solve this problem, we first analyze several sufficient and necessary conditions of the optimal scheme. We then propose a heuristic algorithm based on a dynamic programming algorithm to obtain the optimal solution for a special case where the assignment of all ingots to the soaking pits is known. Based on the results of this special case, we develop a modified biased random-key genetic algorithm (BRKGA), which incorporates genetic operations based on the flower pollination algorithm (FPA) to obtain joint production and distribution schedules for the general problem. Finally, we conduct a series of computational experiments, the results of which indicate that BRKGA-FPA has certain advantages in solving quality and convergence speed issues. [ABSTRACT FROM AUTHOR]

By adopting agile and lean practices, DevOps aims to achieve rapid value delivery by speeding up development and deployment cycles, which however lead to more security concerns that cannot be fully addressed by an isolated security role only in the final stage of development. DevSecOps promotes security as a shared responsibility integrated into the DevOps process that seamlessly intertwines development, operations, and security from the start throughout to the end of cycles. While some companies have already begun to embrace this new strategy, both industry and academia are still seeking a common understanding of the DevSecOps movement. The goal of this study is to report the state‐of‐the‐practice of DevSecOps, including the impact of DevOps on security, practitioners' understanding of DevSecOps, and the practices associated with DevSecOps as well as the challenges of implementing DevSecOps. The authors used a mixed‐methods approach for this research. The authors carried out a grey literature review on DevSecOps, and surveyed the practitioners of DevSecOps in industry of China. The status quo of DevSecOps in industry is summarized. Three major software security risks are identified with DevOps, where the establishment of DevOps pipeline provides opportunities for security‐related activities. The authors classify the interpretations of DevSecOps into three core aspects of DevSecOps capabilities, cultural enablers, and technological enablers. To materialise the interpretations into daily software production activities, the recommended DevSecOps practices from three perspectives—people, process, and technology. Although a preliminary consensus is that DevSecOps is regarded as an extension of DevOps, there is a debate on whether DevSecOps is a superfluous term. While DevSecOps is attracting an increasing attention by industry, it is still in its infancy and more effort needs to be invested to promote it in both research and industry communities. [ABSTRACT FROM AUTHOR]

The purpose of the paper is to present a model of factors affecting the successful project implementation by introducing agility and artificial intelligence to increase the company's competitiveness. In the model, the multidimensional constructs describing the implementation of an agile work environment and artificial intelligence technologies and tools were developed. These multidimensional constructs are agile work environment, agile leadership, agile team skills and capabilities, improving the work of the leader in the project, adopting AI technologies in the project, and using AI solutions in a project. Their impact on successful project implementation and on the company competitiveness was tested. The fundamental reason for conducting this research and developing the model is to enhance the understanding of factors that contribute to the successful implementation of projects and to increase a company's competitiveness. Our developed model encompasses multidimensional constructs that describe the agile work environment and the utilization of AI technologies. By examining the impact of these constructs on both successful project implementation and company competitiveness, we aimed to establish a comprehensive framework that captures the relationship between agility, AI, and successful project implementation. This model serves as a valuable tool for companies seeking to improve their project implementation processes and gain a competitive edge in the market. The research was based on a sample of 473 managers/owners in medium-sized and large companies. Structural equation modeling was used to test the hypotheses. In today's turbulent environment, the results will help develop guidelines for a successful combination of agile business practices and artificial intelligence to achieve successful project implementation, increasing a company's competitiveness. [ABSTRACT FROM AUTHOR]

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

Agile software requirements engineering processes enable quick responses to reflect changes in the client's software requirements. However, there are challenges associated with agile requirements engineering processes, which hinder fast, sustainable software development. Research addressing the challenges with available solutions is patchy, diverse and inclusive. In this study, we use a systematic literature review coupled with thematic classification and gap mapping analysis to examine extant solutions against challenges; the typologies/classifications of challenges faced with agile software development in general and specifically in requirements engineering and how the solutions address the challenges. Our study covers the period from 2009 to 2023. Scopus—the largest database for credible academic publications was searched. Using the exclusion criteria to filter the articles, a total of 78 valid papers were selected and reviewed. Following our investigation, we develop a framework that takes a three-dimensional view of agile requirements engineering solutions and suggest an orchestrated approach balancing the focus between the business context, project management and agile techniques. This study contributes to the theoretical frontier of agile software requirement engineering approaches and guidelines for practice. [ABSTRACT FROM AUTHOR]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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.

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]

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]

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]

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]

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]

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]

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]

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]