Software organizations are increasingly combining agile methodologies and distributed software development (DSD) for efficiently and effectively built software products. There are numerous challenges associated with scaling agile methods in a distributed environment. Our study is intended to explore and prioritize the challenges for scaling agile practices in the DSD environment. This study was divided into 3 stages. In the first stage, 22 challenges were identified from literature review and grouped into 4 categories: management, team, technology, and process based on discussion with experts. In the second stage, an online questionnaire study was conducted to validate the identified challenges. Finally, analytic hierarchy process method was used to prioritize challenges and their categories based on their relative importance. The results highlighted that management is a most significant category as compared with the other categories.Similarly, lack of management commitments, lack of effective communication, lack of knowledge sharing, etc are identified as the most significant challenges that need to be focused by the organizations for scaling agile methodologies. On the basis of the research findings, we could conclude that the identified challenges along with their categories provide a robust framework to scale agile methodologies in the DSD environment. KEYWORDSagile development, AHP, challenges, distributed software development, multiple-criteria decision making INTRODUCTIONOver the last 2 decades, a variety of models and processes have been developed for the effective management of software development activities.Among these, agile is the most significant process that has been introduced to provide opportunities to manage the dynamic behavior of system development activities. 1,2 Agile is a lightweight software development approach that promotes continuous iterations of development and testing throughout the software development life cycle. 2 Various agile methods have been developed, and the most popular among these are extreme programming (XP), crystal, scrum, adaptive software development, and feature-driven development. 3 The underlying philosophy of agile methods is derived from the agile manifesto developed by several system development experts who designed different methodologies on the basis of similar ideals. 2 This philosophy primarily focuses on teamwork, the importance of individuals and their interactions, early product delivery, collaboration with the customers, and effective responses to change requirements. 4 Agile methods were originally designed for small and single-team projects. 2,3 However, few research studies have claimed the successful implementation of agile methods in a distributed environment in large-scale organizations. 3,5 Despite some successful implementations of agile methods, Abbreviations: ANA, antinuclear antibodies; APC, antigen-presenting cells; IRF, interferon regulatory factor J Softw Evol Proc. 2018;30:e1979. wileyonlinelibrary.com/journal/smr

No abstract

No abstract

Software development firms have begun adopting the practice of global software development (GSD). The main reason for the shift toward globalization is the various benefits received by software development firms. However, there are several issues faced by GSD organizations, particularly those associated with software process improvement (SPI). It has been noticed that a formal process improvement approach could assist in successfully executing development activities in GSD. The core objective of this research work is to develop a global software engineering process improvement model (GSEPIM) to assess and improve software process activities in a GSD environment. The proposed model will be developed based on existing models in other domains, an empirical study conducted with GSD practitioners, and an understanding of critical success factors and challenges of SPI. In this study, the first step in the development of GSEPIM is completed by identifying the challenges of SPI in GSD and presenting a solution in the form of a robust framework.

No abstract

Development and operations (DevOps) practices significantly accelerate and automate the continuous delivery and deployment of software systems. However, adopting DevOps concepts is not a straightforward job. Most organizations are not able to keep pace with the rhythm of continuous delivery and deployment, which are key DevOps attributes. Despite the significance of DevOps programs, it is still unknown why software development firms are demotivated or unable to adopt them. We tried to fill this gap by investigating, prioritizing, and developing the taxonomy of the key factors that could impact the adaptation and implementation of DevOps practices. We extracted a total of 16 factors from the available literature and empirically assessed them using the survey approach. The identified factors are further classified into three core categories of the software process improvement (SPI) manifesto. The analytical hierarchy process (AHP) approach was used to calculate the prioritization weight for each factor and present it as a taxonomy. The developed taxonomy provides a roadmap to tackle the key challenges to implementing DevOps and offers suggestions for streamlining DevOps practices.

No abstract

No abstract