Certopolis

Project Management Professional (PMP)

Kanban flow metrics: WIP, throughput, cycle time and SLE

The Kanban Guide names four mandatory flow metrics: WIP, Throughput, Work Item Age and Cycle Time. A team also sets a service level expectation, a forecast of how long an item should take from started to finished, stated as a time and a probability.

The four flow metrics

WIP is the number of work items started but not finished. Throughput is the number of work items finished per unit of time, as an exact count. Work Item Age is the time from when an item started to today. Cycle Time is the time from when an item started to when it finished.

Started and finished mean whatever the team defined in its Definition of Workflow. Teams may use other names for these metrics, such as Flow Time for Cycle Time or Delivery Rate for Throughput. A sponsor who wants the exact number of items finished each week is asking for Throughput.

Definition of Workflow and the SLE

The Definition of Workflow is the team's explicit shared understanding of flow. At minimum it defines the work items, when they start and finish, the states they flow through, how WIP is controlled, explicit policies for moving through each state, and a service level expectation. Its visualization is the Kanban board.

The SLE has two parts, an elapsed time and a probability, such as 85% of items finished in eight days or less. It should be based on historical cycle time. A team that tells a customer 90% of requests should finish within twelve days of starting has set an SLE.

Managing and improving flow

Teams actively manage items by controlling WIP, keeping items from aging unnecessarily with the SLE as a reference, and unblocking blocked work. Controlling WIP should create a pull system: start new work only when there is a clear signal of capacity.

When members dispute when an item may move from review to testing because each applies a different rule, the fix is an agreed explicit policy in the Definition of Workflow. The team does not need to wait for a formal meeting to change its workflow.

Where the exam catches people

  • Believing velocity is a Kanban flow metric: the Kanban Guide's four are WIP, Throughput, Work Item Age and Cycle Time.
  • Believing an SLE is a target or promise with no probability: it is a forecast made of a time and a probability, based on historical cycle time.
  • Believing Work Item Age and Cycle Time are the same: age is for items still in progress, cycle time for finished ones.
  • Believing the project manager should rule on disputes about moving work: the Kanban Guide asks for explicit policies in the Definition of Workflow.

Written from PMI's documentation

Try 3 questions on this

Pick an answer to see why each option is right or wrong.

  1. A sponsor asks a Kanban team for a weekly figure showing the exact number of work items the team finishes in each week. Which of the following flow metrics should the team report?

    Right. In the game that’s Renown for your People building.

    Not that one: B is right. In the game your People building would lose a little Renown, and this question would come back later.

  2. A Kanban team uses its past cycle times to tell a customer that 90% of requests should finish within twelve days of starting. Which of the following has the team set?

    Right. In the game that’s Renown for your People building.

    Not that one: A is right. In the game your People building would lose a little Renown, and this question would come back later.

  3. On a Kanban team, members keep disputing when an item may move from review into testing, because each applies a different rule. Which of the following should the project manager encourage the team to do?

    Right. In the game that’s Renown for your People building.

    Not that one: A is right. In the game your People building would lose a little Renown, and this question would come back later.

    Show the full explanation and doc quotes

    An agreed, explicit policy for moving from review to testing replaces the members' differing private rules.

    Written from kanbanguides.org/the-kanban-guide/2025.5/