CodeScene’s project management metrics let you measure where you spend your costs and how the development activity shifts over time.
This information is useful to bridge the gap between the technical side of the organization and the business side, as you let non-technical managers peek into the codebase from a different point of view.
The Need for Cost Metrics
CodeScene’s project management metrics answer two common questions:
- How shall we prioritize improvements to our codebase?
- How can we follow-up on the effects of the improvements we do? Did we really get an effect out of that design improvement?
Sure, a traditional hotspot analysis already addresses these questions and gives us a tool to prioritize. However, there’s a linguistic chasm between developers and managers here: to a manager, the concept of a “commit” doesn’t carry much meaning. A commit is a technical term that doesn’t translate to anything in the world of managers. At the same time, technical debt with high interest rates and low quality code are important subjects to address. So how can we communicate in the language of a manager while still tying our data back to something that carries meaning for the developers responsible for the code?
CodeScene bridges this chasm by introducing a suite of project management metrics. These metrics combine our existing behavioral code analyses with data from project management tools like JIRA, where CodeScene extracts time-based costs (i.e. minutes of time to completion) or story point reports. We then analyze how those costs are distributed across the different parts of your codebase. This gives you Hotspots measured by cost rather than the more technical metrics. Let’s look at an example.