Agile Metrics: Lead Time, Cycle Time, and Throughput for PMP

Flow Metrics Every PMP Candidate Must Know

Agile teams don't just track velocity and burndown charts. Flow metrics — lead time, cycle time, and throughput — provide powerful insights into how efficiently work moves through the system. These metrics are especially important in Kanban and flow-based approaches, and they appear regularly on the PMP exam.

Lead Time

Lead time measures the total elapsed time from when a work item is requested to when it is delivered to the customer. It includes all wait time, active work time, and any delays in between.

Formula: Lead Time = Delivery Date - Request Date

Example

A stakeholder requests a feature on March 1. The team starts working on it March 8. It's completed and delivered March 15. The lead time is 14 days (March 1 to March 15). Note that the lead time includes the 7 days the request sat in the backlog before work began.

Why Lead Time Matters

Lead time is the customer's metric. The customer doesn't care when you started working — they care about the total time from request to delivery. Reducing lead time improves customer satisfaction and responsiveness.

Cycle Time

Cycle time measures the elapsed time from when active work begins on an item to when it is completed. Unlike lead time, cycle time excludes the waiting period before work starts.

Formula: Cycle Time = Completion Date - Work Start Date

Example

Using the same scenario above: work starts March 8, completes March 15. Cycle time is 7 days. The difference between lead time (14 days) and cycle time (7 days) reveals that half the total time was spent waiting — a significant insight.

Why Cycle Time Matters

Cycle time is the team's metric. It reflects how long the team actually takes to complete work once they start. Improving cycle time requires improving team processes — reducing blockers, improving collaboration, and streamlining handoffs.

Throughput

Throughput is the number of work items completed per unit of time. It's a measure of the team's delivery rate.

Formula: Throughput = Number of Items Completed / Time Period

Example

If a team completes 12 user stories in a two-week sprint, their throughput is 6 stories per week (or 12 per sprint).

Why Throughput Matters

Throughput is the most straightforward measure of delivery capacity. Unlike velocity (which depends on story point estimates), throughput simply counts completed items. This makes it useful for forecasting when story point estimates are inconsistent or unavailable.

How These Metrics Relate

Lead time, cycle time, and throughput are connected by Little's Law, a foundational concept in queueing theory:

WIP = Throughput x Cycle Time

This means: the amount of work in progress equals the delivery rate multiplied by how long each item takes. If you want to reduce cycle time without reducing throughput, you must reduce WIP. This is the mathematical basis for WIP limits in Kanban.

Using Metrics for Improvement

• Lead time is high but cycle time is low? Work is waiting too long before being started. Reduce queue sizes, improve prioritization, or reduce batch sizes.
• Cycle time is high? Work takes too long once started. Look for blockers, excessive WIP, or process inefficiencies.
• Throughput is declining? The team's delivery rate is dropping. Investigate whether WIP is increasing, whether items are getting larger, or whether impediments are accumulating.

PMP Exam Application

The exam may present a scenario with metric data and ask you to identify the problem or recommend an action. The most common exam applications:

• Recognizing that high lead time with low cycle time indicates queue wait time
• Understanding that WIP limits improve cycle time
• Knowing that throughput is used for flow-based forecasting (as velocity is for sprint-based forecasting)
• Applying Little's Law to reason about system behavior

Build your metric analysis skills with PMPprep's data-driven practice questions.