Metric: Code hotspots

[chrisma]

As a team coach, I'd like to gain an insight into the parts of the code that my team focused on during a sprint, i.e. the code hotspots / code churn. This allows me to better understand what the team worked on and to compare the perceptions of team members regarding their changes with the view based on development data.

For example, a sprint could be focused on mostly working on database-focused stories, in which case I would assume changes mostly in the backend files. A sprint focused more on various refactoring would tend to touch many more different files.

Possible measurements:

• Overall number of changed files, overall code churn (sum of lines added & deleted)
• Ranking of files, ordered by amount of times they were changed in sprint commits or by code churn
• Ranking of folders, ordered by amount of times that contained files were changed in sprint commits or by code churn

[chrisma]

This is a metric not based on our collected data sets, so it should have low priority