Project Metrics

Financial burndown

Shows money used over time and tells us the Financial runway available to our teams. Financial burndown can be expressed as the number of sprints available and shared with the team.

Value

Value can be something simple as ROI or system availability. We can extend it to be something more nuanced by adding together the quantities we want delivered from the project; here’s an example:

Value = service reliability + service simplicity + time saved + money saved + best-in-class customer experience + personalization of customer and rep interactions + talent retention

Although some of these appear esoteric they can all be quantified. They are the value a business saw in executing a project; tangible benefits to the business or its customers. Story points are not tangible to customers and don’t make relatable units of value.

Value can be represented as a burndown on each sprint. Also represented as a radar/spider diagram to show team and stakeholders which component of value was delivered and to what extent.

CSAT (Customer Satisfaction)

Indicates how satisfied customers are with the product or service being produced. We can produce lower quality product if our customers are happy with it. CSAT should be gathered every sprint E.g. every incremental value delivery we get CSAT feedback

Team Morale metric

Indicates team morale and ability to process work. Identifies team improvements. We need this because everything delivered is executed by the team. When the team feels good about their work we get higher quality output on time.

Impediment Burndown

Shows project progress in removing impediments from the project. Team estimates each impediment for impact and severity; use relative estimation.

Our impediment burndown is related to waste; can be quantified in money/dollars.

Release burndown

Indicates rate requirements are consumed by the team and the rate new requirements are added to the project. This is used to determine the project's completion date.

Mountain Goat Software have a nice example of a release burndown chart that factors in the effect of adding backlog items to a project’s end date.