Beyond Continuous Delivery: An Empirical Investigation of Continuous Deployment Challenges

Shahin, Mojtaba; Babar, Muhammad Ali; Zahedi, Mansooreh; Zhu, Liming

doi:10.1109/esem.2017.18

Cited by 47 publications

(35 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Interestingly, 6 participants indicating the changes were production-ready at least a few times a month had actual production deployment a few times a year. We argue that the reason for this may stem from factors such as domain constraints and quality concerns [67].…”

Section: Practicing Continuous Delivery and Deploymentmentioning

confidence: 95%

An empirical study of architecting for continuous delivery and deployment

et al. 2018

Self Cite

View full text Add to dashboard Cite

Recently, many software organizations have been adopting Continuous Delivery and Continuous Deployment (CD) practices to develop and deliver quality software more frequently and reliably. Whilst an increasing amount of the literature covers different aspects of CD, little is known about the role of software architecture in CD and how an application should be (re-) architected to enable and support CD. We have conducted a mixed-methods empirical study that collected data through indepth, semi-structured interviews with 21 industrial practitioners from 19 organizations, and a survey of 91 professional software practitioners. Based on a systematic and rigorous analysis of the gathered qualitative and quantitative data, we present a conceptual framework to support the process of (re-) architecting for CD. We provide evidence-based insights about practicing CD within monolithic systems and characterize the principle of "small and independent deployment units" as an alternative to the monoliths. Our framework supplements the architecting process in a CD context through introducing the quality attributes (e.g., resilience) that require more attention and demonstrating the strategies (e.g., prioritizing operations concerns) to design operations-friendly architectures. We discuss the key insights (e.g., monoliths and CD are not intrinsically oxymoronic) gained from our study and draw implications for research and practice.

show abstract

Section: Practicing Continuous Delivery and Deploymentmentioning

confidence: 95%

An empirical study of architecting for continuous delivery and deployment

et al. 2018

Self Cite

View full text Add to dashboard Cite

show abstract

“…Bureaucratic deployment process Ibrahim et al, 53 Shahin et al, 67 Kuusinen et al, 68 Lwakatare et al 69…”

Section: Ch8mentioning

confidence: 99%

“…The bureaucratic process consists of manual and formal tasks that require significant effort and time (e.g., obtaining a single approval from multiple stakeholders). 67 Shahin et al 67 conducted an empirical study to investigate the factors that could impact the continuous delivery aspects of software development. 68 Among their survey respondents, 31.6% said that the continuous deployment process in their organization was highly bureaucratic.…”

Section: Bureaucratic Deployment Process (Ch8)mentioning

confidence: 99%

“…Collaboration is one of the most important factors in the DevOps transformation. 67 It can be achieved through the group efforts of both the development and the operations teams. 2,4 However, organizations' top management are the key stakeholders, and their interest and support are important to the adoption of DevOps concepts.…”

Section: Bureaucratic Deployment Process (Ch8)mentioning

confidence: 99%

“…The main reason for treating the bureaucratic deployment process as a key challenge is that DevOps resolves the disconnect issues between development and operation teams by encouraging close communication, integration and collaboration. 67 Continuous delivery and deployment are the key practices of DevOps, and the organization bureaucratic process can negatively impact them. 67…”

Section: Significance Level Of the Identified Factors (Rq2)mentioning

confidence: 99%

See 2 more Smart Citations

Multicriteria decision‐making taxonomy for DevOps challenging factors using analytical hierarchy process

Khan

Shameem²

2020

J Software Evolu Process

View full text Add to dashboard Cite

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.

show abstract

Readiness model for DevOps implementation in software organizations

Rafi

Akbar

et al. 2020

J Software Evolu Process

View full text Add to dashboard Cite

DevOps is a new software engineering paradigm adopted by various software organizations to develop the quality software within time and budget. The implementation of DevOps practices is critical, and there are no guidelines to assess and improve the DevOps activities in software organizations. Hence, there is a need to develop a readiness model for DevOps (RMDevOps) with an aim to assist the practitioners for implementation of DevOps practices in software firms. To achieve the study objective, we conducted a systematic literature review (SLR) study to identify the critical challenges and associated best practices of DevOps. A total of 18 challenges and 73 best practices were identified from the 69 primary studies. The identified challenges and best practices were further evaluated by conducting a survey with industry practitioners. The RMDevOps was developed based on other well‐established models in software engineering domain, for example, software process improvement readiness model (SPIRM) and software outsourcing vendor readiness model (SOVRM). Finally, case studies were conducted with three different organizations with an aim to validate the developed model. The results show that the RMDevOps is effective to assess and improve the DevOps practices in software organizations.

show abstract

Beyond Continuous Delivery: An Empirical Investigation of Continuous Deployment Challenges

Cited by 47 publications

References 26 publications

An empirical study of architecting for continuous delivery and deployment

An empirical study of architecting for continuous delivery and deployment

Multicriteria decision‐making taxonomy for DevOps challenging factors using analytical hierarchy process

Readiness model for DevOps implementation in software organizations

Contact Info

Product

Resources

About