my takeaways
-
leading indicators (Work Item Age) are relevant for non-finished work, while lagging indicators (Cycle Time, Throughput) are relevant for finished Items
-
kanban metrics are of use in the Scrum Events
- in Sprint Planning the key metric is Throughput, complemented with Work Item Aging for planning on work regarding leftover work from previous sprints.
- in the Daily Scrum Devs concern themselves with the WiP and Work Item Aging.
- Sprint Review revolves around Throughput, complemented by WIP and Cycle Time.
- in Sprint Retrospective we focus on Cycle Time, Throughput & WIP, while taking a look also at Work Item Aging.
Work in Progress
= a number of work items started but not finished
- start and finish are defined by Scrum Team's Definition of Workflow
- an explicit policy that serves as a constraint to help shaping of the flow of work
- historically visualized through the Cumulative Flow Diagram
Cycle Time
= time elapsed between when a work item starts and when it finishes
- start is when the work item is pulled into the workflow
- CT is a lagging indicator visualised in a Cycle Time Scatterplot from which we can read trends, distributions, and look at the anomalies
- enables us to come to the *Service Level Expectation (=amount of time that we expect a work item to be finished in)
Throughput
= number of work items finished per unit of time
- exact count of items, regardless of their size
- measured usually at the finish line of the workflow
- visualized either at a separate run chart, or as the angle of curves on a Cumulative Flow Diagram
- can be read out of the Cycle Time Scatterplot as well
→ !is not velocity!
Work Item Age
= time elapsed between moment when the work item has been pulled into the workflow (=start) and the current time
- complemented with Cycle Time it can show us which items are doing well and which are late
- Work Item Age is the best metric to look at if you want to determine when an item that has already started is going to finish