Recently I stumbled over a smart blog entry about the 'technical debt' (link).
Their technical debt is shown:
- in $ (!!! ouch this hurts)
- in a spider figure
- in the form of numbers you can drill down
- The Code coverage
- The Complexity
- The Code Duplication
- The Violations
- The Comments
If the debt is high the vendor has a problem. Vendors might think they can lock buyers in because they don't check the technical debt. But I am sure time will change and tools like this will be standard in IDEs in 5 to 10 years. Even to check projects in multiple languages.
So for me it's time to face the boss with hard dollars he has to pay back. Sooner or later. The later the more expensive. Let's fight for a technical debt / good metrics analysis as a common procedure!