anchor.diff:  
   ##Mean time to recover
   
  -Mean time to recover (MTTR) is a measure of how long it takes to fix a build failure. This metric is represented as the mean duration. It is the answer to the questions like “how long does it takes to fix a build failure” or “how long does it takes you to restore service during a failed deployment”. 
  +Mean time to recover (MTTR) is a measure of how long it takes to fix a build failure. This metric is represented as a mean duration. It is the answer to questions like "how long does it take you to restore service during a failed deployment". 
   
   #Summary
   
  
positive.code: <% end %>
  
  
  As software and IT become key drivers for innovation in most organizations these days, the speed of software delivery becomes very important to their success. More and more teams are adopting continuous delivery (CD) and expect to benefit from the accelerated feedback loop CD offers. To understand whether you are improving and delivering on your goals, you need to measure you CD process.  
  
  In this blog series, we will share :
  
  
negative.code: 
  #Continuous Delivery
  
  Jez Humble defined continuous delivery on continuousdelivery.com as
  
  >"the ability to get changes of all types - including new features, configuration, bug fixes, and experiments - into production, safely and quickly in a sustainable way."
  
  In practice, a CD pipeline can look like this:
  
  <img src="/assets/images/blog/cd-metrics/gocd-pipelines.png" alt="CD pipelines"/>
  
  On the left of the diagram, the material is a repository such as git or svn. The delivery team commits a change, and your CI/CD server such as GoCD, runs build and unit tests. If these tests fail, the team immediately fixes any problems. The new version with those fixes goes further along the CD pipeline. If tests further down fails, again the team fixes them as quickly as possible. This process happens over and over in the life-cycle of an application. 
  
  #Why measure your CD process 
  
  