anchor.diff:  
   #Why measure your CD process 
   
  -###Measurement, Feedback, and improvement
  +##Measurement, Feedback, and improvement
   
   <img src="/assets/images/blog/cd-metrics/build-learn-measure.jpg" alt="Build, Learn, Measure"/>
   
   If we consider a feedback cycle like “Build, Measure and Learn”, metrics is a way to set specific and measurable goals, direct activities towards achieving those goals, and help you understand if you are achieving those goals.
   
  -###Predict future behavior 
  +##Predict future behavior 
   
   Data will provide you more accurate estimates to your business. For example, if you know your cycle time, you can more accurately answer questions about how long it will take for something to be ready for your customers.
   
   If you are considering parallelizing tasks or removing manual steps in your process, once you have some data about your current process, you can calculate the time savings of these improvement activities. From there, this data could potentially help your organization estimate dollars made or saved by certain specific improvements.
   
  -###Continuous delivery benchmarking
  +##Continuous delivery benchmarking
   
   Once you have some data, the values can be used as your baseline. Those baseline values are key to understanding whether you are improving your own process as well as  key to understanding where you stand relative to “high performing” teams.
   
  
positive.code: 
  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
  
  Failure rate is a measure of the percentage of changes that result in a failure. This metric is represented as a percentage. It is the answer to questions like “what percentage of changes break builds” and “what percentage of deployments result in a service outage”.
  
  ###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”. 
  
  
negative.code: title: Why measure your CD process
  type: post
  author: Aravind S.V and Suzie Prince
  excerpt: "To understand whether you are improving and delivering on your goals, you need to measure you CD process. Here is an overview of where you should begin"
  summary_image: "/assets/images/blog/cd-metrics/measure-cd-process.jpg"
  title_tag_of_header: "Why Measure Your CD Process | GoCD Blog"
  meta_description: "To understand whether you are improving and delivering on your goals, you need to measure you CD process. Here is an overview of where you should begin"
  meta_keywords: "cd metrics, measure continuous delivery, measure devops, mean time to recover, mttr, cycle time, failure rate"
  tags: CD Analytics
  ---
  <% content_for :banner do %>
    <figure>
  <img src="/assets/images/blog/cd-metrics/measure-cd-process.jpg" alt="Why Measure your CD process"/>
    </figure>
  <% end %>
  
  