Once you've had a chance to check out DZone's 2014 Guide to Continuous Delivery, you may be looking for some additional resources to help with your implementation of CD. We dug into the DZone archives and pulled out a handful of DZone's most popular Continuous Delivery resources over the last couple of years:
I went along to hear Dave Farley give a talk on Continuous Delivery and how they’re doing it where he works, at LMAX. It was a really great session and he managed to cover, in quite a short session, a great deal of content from in the book. I’ve put together a highlight of what he covered in the talk, mixed with my own take on things
Here’s what I learned…
In working with development teams at organizations which are adopting Continuous Delivery, I have found there can be friction over practices that many developers have come to consider as the right way for Agile teams to work. I believe the root of conflicts between what I’ve come to think of as traditional agile and CD is the approach to making software “ready for release.”
Earlier this October, I was given the privilege of speaking at JavaOne regarding the fusion of contemporary Continuous Delivery processes and practices with the established and widely-accepted Maven release process. I spoke in detail about the similarities as well as the main differences, and how these techniques and methodologies can be combined to deliver iterations and releases that highlight the need for immediate and ongoing customer feedback, while also satisfying the need for carefully-tested and quality-checked product versions.
A few months ago I attended a talk by Rob Harrop at SkillsMatter on the topic of Continuous Delivery. [Video Here]
Continuous Delivery is all about setting up your development processes such that you can deliver into production much more frequently than is typical, perhaps with multiple releases per day . . . I took away these points from the presentation:
In this talk, Paul Gerrard discusses continuous delivery, particularly as it pertains to long-term requirements. Testing up front, he says, helps to deliver "front-door quality, not back-door quality."
Be sure to check out our Refcardz on the topic as well:
- Preparing for Continuous Delivery
- Continuous Delivery: Patterns and Antipatterns in the Software Lifecycle
And if you haven't yet, don't forget to download DZone's 2014 Guide to Continuous Delivery: