Originally posted by Jac Jones:
the reason is to help justify the amount of refactoring we have had to do - so it would be nice to have something 'objective'.
I my limited experience, management isn't very interested in code quality directly. What would probably help more are the benefits of the improved code quality, such as
"If we would have had to do X two years ago, it would have taken us weeks, but because of the improved code quality, it is now only taking hours."
or
"Implementing feature X is a breeze today. Two years ago it would have been near to impossible to implement, because the code was so much more rigid."
Having numbers for your code quality might be able to support those statements, but if my experience is typical, it's unlikely to work if standing alone.
Hope this helps...
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus