Edit this page on GitHub

Home > docs > playbooks > metrics > Code Inventory

Alexis Dixon , Bryan Finster , Nathan Nicholson , Preston Gibbs

Code Inventory

The lines of code that have been changed but have not been delivered. This can be measured at several points in the delivery flow, starting with code not merged to trunk.

What is the intended behavior?

Reduce the batch size of individual changes and reduce the duration of branches. Small batches are needed for effective quality feedback. Stale branches represent risk of lost change or merge conflicts that result in additional manual steps that add risk of defect creation.

How is it improved?

  • Focus on continuous integration behavior where changes are integrated to the trunk and verified multiple times per day.

How is it gamed?

  • Code on forks is not visible to be measured. However, forking should not be used for team development. Branching is more appropriate.

Guardrail Metrics

The following metrics could degrade if not tracked with this metric

  • Quality can decrease as quality steps are skipped in the name of speed.