The Case for Continuous Delivery

Interest in implementing continuous delivery is increasing, especially when people discover the approach’s benefits and vast potential, but many companies don’t know where to start. The process requires that an organization integrate a culture of continual software improvement and delivery. For most, that means acquiring a fundamental new mindset.

The Case for Continuous Delivery, written by four of the best current DevOps thinkers, aims to help companies get moving along this crucial path. It is the first in a series of six mini–e‑books sponsored by Zend that offers a compelling collective argument for using continuous delivery in software development.

In this installment, for example, IT Revolution Press researcher Gene Kim argues how continuous delivery represents a “staggering” global opportunity. If IT waste were halved and the resulting savings properly redeployed, he writes, the industry could generate $3 trillion in value annually—more than Germany’s entire economic output. “The potential economic impact to productivity, standards of living, and prosperity almost makes this a moral imperative,” states Kim.

In his essay, Ido Ben Moshe, Zend’s vice president of Global Support & Professional Services, describes a workbook he has created that can allow anyone to calculate expected return on investment (ROI) from continuous delivery. That workbook can be a powerful tool for convincing company leaders to make the commitment. “The business benefits of continuous delivery are very real,” Moshe writes, “and the numbers prove it, time and again.”

Every author makes an equally compelling case, sometimes through personal experiences. We learn, for instance, that Chris Hilton, lead consultant at ThoughtWorks, began writing software to amuse his brother—his first “user”—and still approaches code the same way. Continuous delivery only sharpens that focus, he argues, by shortening the distance between creator and user.

Mike Miller, co-founder and chief scientist at Cloudant, reveals that his past role as a physicist on the Large Hadron Collider project prepared him well for continuous delivery. In fact, it’s really all he has ever known. “The first lines of production software I ever wrote went live a few minutes after commit,” Miller writes. “Thank goodness they passed the test!”

Essays also include bullet-point summaries of key lessons these experts learned while taking their own companies to the next level of DevOps and working closely and collaboratively with their teams to ship high-performing, continually improving code.

Lessons from 29 DevOps Experts on the Best Way to Make the Transition to Continuous Delivery provides best practices and advice from the top DevOps industry leaders. If you’re interested in learning more about how to implement continuous delivery, this book covers each step: getting started in continuous development, integrating and automating the process, getting the team on board, changing the culture, and best practices for the future. Download the full e‑book now to take advantage of these expert insights and determine whether continuous delivery is right for your business.

The Case for Continuous Delivery from Zend Technologies

The following two tabs change content below.

    Kevin Featherly