Professional learning guide
Agile Delivery and Flow Metrics Guide
Use empirical evidence from completed work, WIP, throughput, lead time, cycle time, burndown, and velocity to improve predictability.
Core concepts
Build the mental model first
- Work in progress
- Started work that has not satisfied the definition of done.
- Throughput
- Number of work items completed per unit of time.
- Cycle time
- Elapsed time from active-work start to completion.
- Lead time
- Elapsed time from customer request to delivery.
Formula reference
Calculate—and understand what direction means
| Measure | Formula | Interpretation |
|---|---|---|
| Little’s Law | WIP = Throughput × cycle time | Applies to a stable system using consistent units. |
| Velocity average | Completed points ÷ sprints observed | Team-specific historical planning signal. |
| Flow efficiency | Active time ÷ total lead time × 100 | Share of elapsed time spent actively working. |
Worked reasoning
Delivery slows while everyone is busy
Situation
WIP has doubled, throughput is flat, and cycle-time percentiles are increasing.
Manager’s approach
Stop starting lower-priority work, visualize queues, identify the constrained workflow state, and help finish blocked items.
Takeaway
Local busyness is not system productivity. Limiting WIP often improves flow without increasing individual utilization.
PMP lens
What to remember in scenario questions
- Adaptive teams inspect and adapt using empirical results.
- Velocity should not compare teams or individuals.
- A product owner orders value; the team selects work it can complete.
- Servant leadership removes impediments and enables team ownership.
Common doubts
Questions learners ask
Should incomplete work count toward velocity?
No. Count only work that meets the agreed definition of done.
Why use percentiles for cycle time?
A range communicates variability and forecast confidence better than one average.
Can story points be converted to hours?
They represent relative effort or complexity within a team and should not be treated as a universal time conversion.
Practice tools
Apply agile & flow concepts
Sprint Burndown
Compare remaining work with the sprint trajectory.
Open calculator →Agile Velocity
Use completed work history for release forecasting.
Open calculator →Throughput
Measure completed work per unit of time.
Open calculator →Cycle Time
Measure how long active work takes to finish.
Open calculator →Lead Time
Measure end-to-end customer waiting time.
Open calculator →Cumulative Flow
Visualize WIP, flow stability, and bottlenecks.
Open calculator →Agile Team Capacity Calculator
Estimate usable team capacity for a sprint after applying availability and focus factors.
Open calculator →