From agile point of view, technical debt is a big topics especially after running agile/scrum for a while, team are used to leave technical debt into next iteration, not everyone want to decrease it, though agile coach mentioned/remind this. While with the one sonar plugin available, team will change their mind.
After successful deploy sonar (see posts Maven, Sonar with Nexus, so wierd), I started to install more useful plugins, you can see reference Code Quality Management Tool Sonar Provides Design and Architecture Metrics
Let’s start a real example below after I enabled the Technical Debt
From technical point of view, it is just another view from different quality metric (using different fomula), but the result is excellent, since when I show this to people, they quickly notice, “Ooh, this project cost lots to maintain (294$)”
Forget to mention, deploy those plugins just needs “download, copy, restart”, no huge cost for integration.
more about Technical debt: http://thoughts.inphina.com/2010/04/03/dont-judge-an-application-by-looks/
As I said, CI and automation provides better feedback
All those plugins can be found http://docs.codehaus.org/display/SONAR/Sonar+Plugin+Library/
So my suggestion
- deploy SONAR first
- install technical debt plugins to track it.