anchor.diff:  <% 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.  
  +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 :
   
  
positive.code: 
  #What metrics are important to measure?
  
  Once you introduce a CD pipeline and have established your path-to-production, the next step is to monitor its efficiency. We do not suggest measuring everything. At the high level here are the four metrics that we suggest using to help monitor your CD process. We’ll go deeper into details in future parts of the series.
  
  ##Throughput
  
  Throughput is a measure of how frequently your team deploys code. This metric is represented as a percentage. It is the answer to the question “how often does code reach a certain point in the CD pipeline”
  
  ##Cycle Time
  
  Cycle time is a measure of how long it takes from committing code to deploying it to a production environment. This metric is represented as a duration. It is the answer to the question “how long does it take from committing code to deploying it to a production environment”.
  
  ##Failure Rate
  
  
negative.code: 
  ##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 a mean duration. It is the answer to questions like "how long does it take you to restore service during a failed deployment". 
  
  #Summary
  
  