anchor.diff:  
   In the diagram above, we calculate time from a commit (at the start of a CD pipeline) until when that code commit goes to production (at the end of the CD pipeline). Although other points in the CD pipeline have happened multiple times, it was only after three days that the deployment happened, so we calculate the lead time for that commit as three days.
   
  -##Why Lead Time is Important
  +##**Why Lead Time is Important**
   
   Lead time is a key element of lean theory. Focusing on reducing lead time will allow you to look at your process as a whole and understand the slowest parts. If teams and organizations only concentrated on lowering lead time they would improve and add more value to their organization. 
   
  
positive.code: <% end %>
  
  
  ##How Long Does It Take From Code Commit to Production?
  
  This is the third post in the series - Actionable Continuous Delivery Metrics. In the previous posts, we gave an overview of why and what metrics matters to your CD process as well as an in depth discussion on deployment frequency. In this post, we’ll get deeper into lead time. 
  
  
negative.code: 
  Finally, we recommend only considering the “delivery” part when calculating lead time for your CD process. If you define the start time from first line of code, and remove the “fuzzy front-end”, which include activities like requirement gathering, system analysis, prioritization etc, it is a simple and very practical metric to calculate.
  
  ##**An Example: How to Use Lead Time**
  
  We will continue with the hypothetical scenario we used in part 2 of the series, in this scenario, the development team received the complaint from their stakeholders that they didn’t get value very often. 
  
  