Skip to main content

Continuous Delivery

Image
By
Continuous Delivery is a software development practice where software is always in a releasable state.  Teams produce software in short cycles, ensuring that the software can be reliably released at any time. By relying on automated testing and deployment, as well as ensuring collaboration and communication between development and operational teams (DevOps), the goal of building, testing, and releasing software faster and more frequently can be achieved. This approach can help to reduce the cost, time and risk of delivering changes by allowing for more incremental updates to applications and configuration items (CIs) into production. 

A straightforward and repeatable deployment process is important for continuous delivery and will be critical for operational processes such as Change Management and Release and Deployment Management to be agile and robust in the DevOps environments where continuous delivery will be part of best practices.  

Continuous Delivery is sometimes confused with Continuous Deployment. Continuous Deployment means that every change is automatically deployed to production. Continuous Delivery means that the team ensures every change can be deployed to production but may choose not to do so, usually due to business reasons. In order to do Continuous Deployment one must be doing Continuous Delivery. (1)
Continuous delivery is enabled through the deployment pipeline. The purpose of the deployment pipeline has three components: Visibility, Feedback and Continually Deploy. (2)
·       Visibility – All aspects of the delivery system including building, deploying, testing and releasing are visible to every member of the team to promote collaboration.
·       Feedback – Team members learn of problems ASAP when they occur so that they are able to fix them as quickly as possible.
·       Continually Deploy – Through a fully automated process you can deploy and release any version of the software to any environment.
Continuous Delivery also requires that whenever anyone makes a change that causes an automated test to fail, breaking the deployment pipeline, the pipeline and all associated systems must be brought back into a deployable state.  In some cases, the Standard Operating Procedure (SOP) may be to have continuous integration and deployment reject any changes that take the code or configuration out of a deployable state.

Remember it is all about “Flow” in which continuous delivery is just one of many practices utilized in the “First Way”.

For more information on DevOps, Agile and IT Service Management training and certification:  www.itsmacademy.com

1.       http://martinfowler.com/bliki/ContinuousDelivery.html

2.       Duvall Paul /Continuous Delivery: Patterns and Anti-Patterns in Software Lifecycle" 
Labels:

Comments

Post a Comment

Popular posts from this blog

Four Service Characteristics

By
Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...
Post a Comment
Read more

What is the difference between Process Owner, Process Manager and Process Practitioner?

By
This article was originally published in 2015. With the Introduction of ITIL 4, some of the concepts have changed in ways that are described below. ITIL 4 has also introduced new roles, as explained in our blog ITIL 4 and the Evolving Role of Roles . Before we dive into the difference between these roles, let’s first look at a key update in ITIL 4 – the shift from processes to practices. ITIL 4 has evolved to focus on holistic practices vs. isolated processes. By definition, a practice is a set of organizational resources designed for performing work or accomplishing an objective. For example, the purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. All organizations recognize the need to allocate resources to the management of incidents and mature their capabilities in that area. In ITIL 4, each practice includes resources based on the four ...
1 comment
Read more

What Is A Service Offering?

By
The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...
Post a Comment
Read more