<p>The idea of lead time is that when the customer asks for something, a clock starts ticking in their head and that clock stops when they have it in their hands. Therefor, a feature's lead time would be from when the request is received (this usually corresponds to adding it to the backlog) until it is delivered and usable to the requestor. </p>

<p>Full disclosure, I haven't read Accelerate, but since Forsgren is using an existing term and it seems it's being used correctly, I am referring to the proper definition of the term.</p>

<p>Now, that isn't to say all those other things you mention aren't valuable. They may be. They may even be more valuable to you than lead time. They just aren't lead time.</p>

CC BY-SA 4.0
2020-02-05T17:54:51.760Z
2020-02-05T17:54:51.760Z
Daniel
<p>I'm currently revisiting Accelerate by Nicole Forsgren and I'm looking at her metrics for measuring high performance. Specifically Lead Time which she defines as:</p>

<blockquote>
  <p>Lead Time is the time it takes from the customer making a request to the request being satisfied.</p>
</blockquote>

<p>She also notes that</p>

<blockquote>
  <p>there are two parts to the lead time: the time it takes to design and validate a product or feature, and the time to deliver the feature to customers.</p>
</blockquote>

<p>However, in a normal scrum team stories are added and prioritised to the backlog all the time. Something may be added and then deprioritized or even cancelled. when exactly does a customer "make a request?"</p>

<p>Is it:</p>

<ul>
<li>When it's added to the backlog?</li>
<li>When it's accepted in Sprint planning?</li>
<li>When it's "accepted" and estimated?</li>
<li>Somewhere in between?</li>
</ul>

<p>I'm less worried about "delivered" that feeds into definition of done.</p>

<p>Any "word of god" statements from Forsgren herself would be preferred.</p>

<agile>
How to measure Lead Time for a Scrum Team
Liath
# How to measure Lead Time for a Scrum Team

(Asked by: username_0 on 2020-02-05)

I'm currently revisiting Accelerate by Nicole Forsgren and I'm looking at her metrics for measuring high performance. Specifically Lead Time which she defines as:

> Lead Time is the time it takes from the customer making a request to the request being satisfied.

She also notes that

> there are two parts to the lead time: the time it takes to design and validate a product or feature, and the time to deliver the feature to customers.

However, in a normal scrum team stories are added and prioritised to the backlog all the time. Something may be added and then deprioritized or even cancelled. when exactly does a customer "make a request?"

Is it:

* When it's added to the backlog?
* When it's accepted in Sprint planning?
* When it's "accepted" and estimated?
* Somewhere in between?

I'm less worried about "delivered" that feeds into definition of done.

Any "word of god" statements from Forsgren herself would be preferred.

**Tags:** agile


---

## 1 answers

### Answer by username_1 on 2020-02-05. Score: 3

The idea of lead time is that when the customer asks for something, a clock starts ticking in their head and that clock stops when they have it in their hands. Therefor, a feature's lead time would be from when the request is received (this usually corresponds to adding it to the backlog) until it is delivered and usable to the requestor.

Full disclosure, I haven't read Accelerate, but since Forsgren is using an existing term and it seems it's being used correctly, I am referring to the proper definition of the term.

Now, that isn't to say all those other things you mention aren't valuable. They may be. They may even be more valuable to you than lead time. They just aren't lead time.


---

