Code Change Rate

Code Change Rate

What is this metric?

This metric measures the rate of code changes the team produces throughout the iteration. Notice that this metric takes into account any type of code change: new code, refactored code and rework.

Why is it important?

It is a great signal to the pace of work. While project management systems hold the task record and its state, this metric is git based and will give you the true 'in progress' indication whether it's new value, bug fixes or non functional work.

How is it calculated? 

This metric is calculated by summing all the code line changes and dividing them by the days passed in the iteration. 

How to improve?

If you are 2-3 days into an iteration and this value is still at the lower end it could indicate that tasks are not well defined. To release this bottleneck, consider revisiting tasks requirements.

What is the industry standard?

The industry standard line is based on the metrics values in all LinearB community teams. You can read all industry benchmarks here: Metrics Community Benchmarks

How did we do?

Powered by HelpDocs (opens in a new tab)