top of page

What measures improves - Peter Drucker

Metrics

Every development manager is (or should be) tasked with measuring the performance of their teams. The first step to success is to select the metrics you measure. The lists below are the metrics I have found to be most useful.

Most of the metrics are based on story points but I do find value in counting the work items. All metrics, unless specified otherwise, are measured on a per-sprint basis.

Name
Description
Formula
Key Metric
Initial Planned
The number of story points initially pulled into the sprint during sprint planning
Yes
Injected
The number of story points injected into the sprint after the start.
Yes
Removed
The number of story points removed from the sprint to make room for injections.
Yes
Sprint Total
The total number of story points committed to during the sprint.
[Planned] + [Injected] - [Removed]
Yes
Completed
The number of story points completed during the sprint.
Yes
Delivered vs Planned %
The % of story points completed vs the # of points initially planned
[Completed] / [Initial Planned]
Yes
Carryover %
Percent of points carried over from the previous sprint
No
Carryover #
# of points carried over from the previous sprint
No
Average Value
The total # of points in the sprint divided by the number of items in the sprint.
[Sprint Total]/[Sprint Total (Items)]
Yes
Average Committed (4-Sprint)
The average of the # of points committed to in the last sprints.
Yes
Points/Dev Day aka PDD
Measured efficiency of your dev team.
[Completed] / [Dev Days]
Yes
Average Completed (4-sprint)
The average number of points completed in the last 4 sprints
Yes
Average Delivery % vs Commitment (4-Sprint)
The rolling average of the % of points completed vs committed to.
No
Average PDD (4-Sprint)
The rolling average of points-per-dev-day for the last 4 sprints.
Yes
Commit vs Average Differential
The difference between the commitment amount at the start of a sprint and the average delivery amount for the last 4 sprints.
Yes
bottom of page