Work Type is a representation of the split types of work done, I.e. New work or Maintenance work. Lines of Code and Rework of Own or Others work is also mentioned in some of the graphs. As a general rule, New Work should preside over Maintenance Work as it shows innovation and growth within the team.

This metric quite literally gives the percentage of work considered New within the system.

This metric helps quickly identify whether the team is using their time productively and if the system is productive as a whole. The higher the number the better as it shows how much work and time was spent on making new features rather than doing maintenance on old code.

It is a quick way to determine whether progress is being bottlenecked by old, redundant code or not. Further actions include drill-down but may also include further team training such that the same problem is less likely to happen in future.
​

These two graphs are a visual representation of the breakdown of work types within weekly cycles.

These charts give another perspective on where work is allocated, this time showing all the types of work done. Typical red flags are:

It is a more in depth way of finding out where the other types of work are going. If there is a problem with New Work Percentage then this is the place to find where all the other work is going and fix it afterwards.

These two graphs are a visual representation of Merged code change (lines of code) by work type across time.

These charts give yet another perspective on where work is allocated, this time giving an even more in-depth view of how the codebase has changed. Typical red flags are:

These metrics are another way of finding out what section the most work has been put into and by extension, which areas may need to be investigated further to find the source of a potential blocker.
​

Here the graph shows in which language the different types of work’s code was written.

This metric should help you figure out what training and what area the developers should be most comfortable coding in. This is not a graph to find potential blockers but is included as further knowledge about the teams own work. If there was a language with significant rework own, then expertise and training may be needed in this area.

This metric is useful in filling in any knowledge gaps for any contributors and finding the most important languages for developers to learn.