Since the inaugural DevOpsDays event was hosted by Patrick Debois in 2009 and the “Continuous Delivery” book by Dave Farley and Jez Humble was published in 2010 the interdependent disciplines of Continuous Delivery and DevOps have enjoyed rapid adoption and already attained mainstream status. Creating an automated deployment pipeline and increasing collaboration between Development and Operations teams offers tremendous benefits to an organisation, with the potential for improvements in quality, lead times, and operability that will reduce costs and increase product revenues.
However, Continuous Delivery and DevOps are hard. In many organisations the creation of an automated deployment pipeline is impeded by significant technology challenges, and encouraging Development and Operations teams to work together can seem impossible. How do you automate an unversioned release script run from different unversioned servers for years? How can siloed Development and Operations teams work together when one party is incentivised by features and the other by stability?
We have seen Continuous Delivery and DevOps work in the wild. Steve worked on the greenfield LMAX pipeline and the brownfield Sky Network Services pipeline, and has seen how rapidly releasing software can improve quality and reduce risk. Matthew helped to introduce Continuous Delivery and a DevOps culture at thetrainline.com, and has seen over many years how a focus on operability delivers better software systems. Furthermore, at the monthly London Continuous Delivery meetup and the annual PIPELINE conference we hear how other practitioners have applied the principles and practices of Continuous Delivery and DevOps to their own organistions, and regardless of results there are always points of interest and lessons to be learned.
We want to help others on their Continuous Delivery and DevOps journey, by sharing the experiences of those who have been there before – what worked, what didn’t, and the highs and lows of trying to build quality into an organisation. We also want to raise the profile of other practitioners in this area, and contribute in some small way to improving diversity within the IT industry. We hope Build Quality In helps you on your own journey.
We would like to thank all of our contributors plus Dave Farley and Patrick Debois for their all-important contributions to this book. Thanks also go out to Kevlin Henney for the initial advice, LondonCD for the encouragement, Peter Armstrong and the Leanpub team for the help, and Laura Kirsop and the Code Club team for the inspiration.
Finally, we would like to thank our long-suffering families. We couldn’t do this without you.
Steve Smith and Matthew Skelton, 2014