Continuous Delivery

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"

Comments

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 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 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. Note: Goods may not always be provided for every Service Offe

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search