Book Review: Continuous Delivery by Jez Humble and David Farely

By Jez Humble and David Farley

Continuous Delivery from Jez Humble and David Farley is an important contribution to the field of software development. It takes continuous integration to the logical conclusion and covers how to set up a continuous integration system, delving into everything from check-in to delivery to production. It doesn’t state you have to deliver directly in production, but it will explain how technically it is achievable to do that and what enormous benefits this brings to your organization.

Continuous delivery consists of three parts: 1) Foundation, 2) Deployment Pipeline, and 3) Delivery Ecosystem.

The first four chapters cover the fundamentals the rest of the book is based on. The first chapter provides some problems with more traditional approaches and also introduces some principles extracted out of continuous delivery. The next three chapters cover topics that provide the basics of continuous delivery. Someone involved with agile development for a while is probably aware of most of this and it will be a quick read. For new people, these chapters provide a quick introduction to these topics so that you can understand the rest of the book. The chapters are: “configuration management,” “continuous integration,” and “implementing a testing strategy.”

The second part is the core of the book. It explains the continuous delivery pipeline. This pipeline is a series of stages (a series of continuous integration systems) each stage covering higher-level wider-range of testing so that the confidence in the product increases the later the stage in the deployment pipeline passes. The stages the authors recommend in the deployment pipeline are: commit, acceptance, capacity, manual, production. Each of these stages (except for manual) has its own chapter which explains tools and practices that the authors have found useful in that stage of the deployment pipeline. The part also contains an additional ‘foundation’ chapter about build and deployment scripting.

The last part of the book is one that I, myself, found most interesting which covers perhaps some ‘advanced’ topics. The part is called “delivery ecosystem” and the chapters aren’t directly related to each other, but each chapter covers a common topic related to the deployment pipeline. Chapter 11 talks about managing and automating your infrastructure as part of your build also. It introduces a vast amount of topics related to automation (puppet, chef), virtualization, cloud computing and monitoring. Unfortunately, the book is only able to touch a little upon each of these topics as each of them could easily fill several others books (and they do!). Chapter 12 covers a very frequent problem in testing and test automation related to managing data. It explains several different approaches and then evaluates them and shares the experiences and recommendations of the authors. Managing test data is a common problem and is rarely covered in the amount of detail as this book does. Chapter 13 discusses different scaling options by componentizing the product and what effect this has on the continuous deployment pipeline (basically adding another dimension to the pipeline). Chapter 14 is about version control and can be summarized as “avoid branching” but the authors do a good job explaining that message and why the alternatives are indeed worst. Chapter 15 was short (I slightly disliked this chapter), and about managing continuous delivery. It felt like the standard “and now… what actions to take”-chapter. It was a bit shallow though.

When the book was published, I read it through rather quickly and liked it, however I didn’t appreciate the depth of the book yet. I re-read it the second time more thoroughly and enjoyed the careful comparisons and explanations of the recommendations of the authors. They shared the experiences they have had very clearly. The book is interesting to me as it covers a vast area and thus it is hard to not touch everything shallowly, but they don’t do that. They go in more depth at the points where the authors feel it is appropriate (for example, parts that are controversial or often done differently).

The book isn’t perfect though! As some other reviewers pointed out, it is repetitive and should have been thinner. I agree with that. Also, sometimes the book side-tracks in interesting facts that are unlikely to help the reader a lot, such as the history of version control. Next, the book contains some very basic things that could have perhaps been left out (or put as appendix), such as an explanation of maven. Lastly, the book sometimes contradicts itself such as the recommendation to do things “at the beginning of the project” but then later stating that “at the beginning of the project, all these decisions will change”. There I still felt the influence of standard ‘project’ thinking.

With all these drawbacks, I still decided to rate the book five stars because I do think it is a very influential and important book. It tells and shows that continuous delivery is not just a perfection state but that it can be achieved today. Not only that, it can be achieved in larger projects, not just small web projects. This is a huge contribution to the industry and I think and hope that the practices of continuous delivery will become standard practices everywhere. Excellent read (except for the repetition) and highly recommended.

Bas Vodde
Bas Vodde works for Odd-e, a company which supports organizations in improving their product development, mostly in Asia. Bas Vodde is a coach, programmer, trainer, and author related to modern agile and lean product development. He is the creator of the LeSS (Large-Scale Scrum) framework for scaling agile development. He coaches organizations on three levels: organizational, team, individual/technical practices. He has trained thousands of people in software development, Scrum, and modern agile practices for over a decade.
Bas Vodde on Linkedin

The Related Post

How to ensure a successful test-driven environment In order to ensure a higher quality product is released in the end, many teams have turned to test-driven development. Under this scenario, quality assurance metrics professionals first create various QA tests, and then software engineers code based on these tests, typically while using a robust enterprise test management ...
DevOps may be the next big buzzword, but Test teams really need to focus on its little sister, Continuous Delivery If you pay attention to trends in software development—from the perspective of what some sophisticated teams are doing, what articles and books are being written, to conference topics, you may have noticed the tools being ...
LogiGear Magazine June Issue 2018: TESTING in DEVOPS
Continuous Testing and Continuous Monitoring What is the goal of Continuous Integration? Is it to enable Continuous Delivery of the code developers’ produce out to users? Yes, eventually. But first and foremost it is to enable ongoing test and verification of the code. It is to validate that the code produced and integrated with that ...
Sauce Lab’s Perspective on Integration with Continuous Testing The term ‘DevOps’ implies that implementing an effective development and production workflow is as easy as developing the collaborative interaction between developers and IT operations. On the surface, DevOps may appear as a simple and straightforward idea but, as you will find out, there is more than meets ...
From the culture shift, to differences in Agile, Dave Farley and Michael Hackett discuss the nitty gritty of Testing in DevOps. For this issue of LogiGear Magazine, our very own Michael Hackett sat down with one of the godfathers of Continuous Delivery, David Farley. In this exclusive interview, David discusses how test teams and automation ...
As a software development company, what is your goal? What is the one thing you feel you need to do to ensure you have a job at the beginning of each wonderful work week? The answer is actually quite simple; You need to deliver a quality product. Like how I used the word simple? Although the answer I ...
LogiGear Magazine June Testing in Continuous Delivery Issue 2017
DevOps has been described as Agile on Steroids; DevOps has also been described as Agile for Operations/IT. I like both of those descriptions. Many organizations want Development, Test, and Operations teams to move to DevOps now. DevOps is a big topic, but DevOps is not the focus of this article. We will not be talking ...
This post is part of the Pride & Paradev series With continuous deployment, it is common to release new software into production multiple times a day. A regression test suite, no matter how well designed, may still take over 10 minutes to run, which can lead to bottlenecks in releasing changes to production. So, do ...
LogiGear University announces the launch of a new, free video series on Testing in DevOps and Continuous Testing which is available today.
In this article, I share some of my experiences and observations on training teams, mainly in corporate settings. The operative word here is “team”, not “individual”. When training teams or groups in an organization, many of the considerations and benefits are different than those for the individual. We’ll examine those differences and I will share successful solutions. ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe