The Community for Technology Leaders
2015 Agile Conference (AGILE) (2015)
National Harbor, MD, USA
Aug. 3, 2015 to Aug. 7, 2015
ISBN: 978-1-4673-7153-7
pp: 1-10
ABSTRACT
Continuous deployment speeds up the process of existing agile methods, such as Scrum, and Extreme Programming (XP) through the automatic deployment of software changes to end-users upon passing of automated tests. Continuous deployment has become an emerging software engineering process amongst numerous software companies, such as Facebook, Github, Netflix, and Rally Software. A systematic analysis of software practices used in continuous deployment can facilitate a better understanding of continuous deployment as a software engineering process. Such analysis can also help software practitioners in having a shared vocabulary of practices and in choosing the software practices that they can use to implement continuous deployment. The goal of this paper is to aid software practitioners in implementing continuous deployment through a systematic analysis of software practices that are used by software companies. We studied the continuous deployment practices of 19 software companies by performing a qualitative analysis of Internet artifacts and by conducting follow-up inquiries. In total, we found 11 software practices that are used by 19 software companies. We also found that in terms of use, eight of the 11 software practices are common across 14 software companies. We observe that continuous deployment necessitates the consistent use of sound software engineering practices such as automated testing, automated deployment, and code review.
INDEX TERMS
Software, Companies, Internet, Testing, Software engineering, Facebook, Industries,follow-up inquiries, agile, continuous deployment, continuous delivery, industry practices, internet artifacts
CITATION
Akond Ashfaque Ur Rahman, Eric Helms, Laurie Williams, Chris Parnin, "Synthesizing Continuous Deployment Practices Used in Software Development", 2015 Agile Conference (AGILE), vol. 00, no. , pp. 1-10, 2015, doi:10.1109/Agile.2015.12
78 ms
(Ver 3.3 (11022016))