Book Image

Continuous Delivery and DevOps ??? A Quickstart Guide - Third Edition

By : Paul Swartout
Book Image

Continuous Delivery and DevOps ??? A Quickstart Guide - Third Edition

By: Paul Swartout

Overview of this book

Over the past few years, Continuous Delivery (CD) and DevOps have been in the spotlight in tech media, at conferences, and in boardrooms alike. Many articles and books have been written covering the technical aspects of CD and DevOps, yet the vast majority of the industry doesn’t fully understand what they actually are and how, if adopted correctly they can help organizations drastically change the way they deliver value. This book will help you figure out how CD and DevOps can help you to optimize, streamline, and improve the way you work to consistently deliver quality software. In this edition, you’ll be introduced to modern tools, techniques, and examples to help you understand what the adoption of CD and DevOps entails. It provides clear and concise insights in to what CD and DevOps are all about, how to go about both preparing for and adopting them, and what quantifiable value they bring. You will be guided through the various stages of adoption, the impact they will have on your business and those working within it, how to overcome common problems, and what to do once CD and DevOps have become truly embedded. Included within this book are some real-world examples, tricks, and tips that will help ease the adoption process and allow you to fully utilize the power of CD and DevOps
Table of Contents (13 chapters)

Some common problems

During your elephant exposure, you will have surfaced some problems with how you are currently delivering software. You will also start to consider the problems within your culture, environment, and the behaviors being exhibited.

The presumption here is that the problems identified are the commonplace issues related to most software delivery processes within most businesses around the globe. These will include some of the following:

  • Waste from having too many handover and decision points in the process
  • Waste due to unnecessary wait time between steps
  • Many software changes are packaged up into large, complex big bang releases
  • Large and infrequent releases breed an environment for escaped defects and bugs and mistrust between those delivering change and those supporting it
  • Releases are seen as something to dread rather than a positive opportunity for change...