Posts filed under: Continuous Delivery

Continuous Delivery

This page contains posts by Jayme related to Continuous Delivery. This term was coined by Jez Humble of Thoughtworks. He referenced the first principle of the Agile Manifesto, which states:

“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”

Continuous delivery at its core is a set of patterns and practices that enable a company that builds software products and services to reduce their cycle time. Cycle time is a measurement of the time it takes from when someone has an idea, until it is delivered to customers.

The primary innovation of Continuous Delivery is the concept of a deployment pipeline. The deployment pipeline uses technology to automate the processes typically used to release software.

Continuous Delivery is closely related to the DevOps movement, in that developers and operations must typically work together closely to make it a reality. However, many companies today still have developers and operations working together but have not built a complete deployment pipeline. Conversely, many companies have built a deployment pipeline, but still keep development and operations reporting under separate departments.


My post yesterday touched on one of the subjects related to software development that has really crystallized some of the process breakdowns I see in too many organizations out there. There is much time spent measuring developer output, but missing...
When teams develop software, they use products from other vendors to aid them in following their chosen process. Usually data is captured during development that can be used to create reports or do analysis from these other vendors’ products resulting...
The goal of developing any software should be to provide functionality useful to the majority of its users. While doing business analysis or writing user stories for a feature of a project (especially those that are an attempted re-design of...
I saw Martin Fowler speak in Austin a couple years ago and one part of his talk was on continuous integration, and specifically the downsides of feature branching. Feature branching is essentially where a main “trunk” of source for a...
>