title: How would you measure code "quality" across a large project
body: <p>I'm working on a quite large project, a few years in the making, at a pretty large company, and I'm taking on the task of driving toward better overall code quality.</p>
  
  <p>I was wondering what kind of metrics you would use to measure quality and complexity in this context.  I'm not looking for absolute measures, but a series of items which could be improved over time.  Given that this is a bit of a macro-operation across hundreds of projects (I've seen some questions asked about much smaller projects), I'm looking for something more automatable and holistic.</p>
  
  <p>So far, I have a list that looks like this:</p>
  
  <ul>
  <li>Code coverage percentage during full-functional tests</li>
  <li>Recurrance of BVT failures</li>
  <li>Dependency graph/score, based on some tool like nDepend</li>
  <li>Number of build warnings</li>
  <li>Number of FxCop/StyleCop warnings found/supressed</li>
  <li>Number of "catch" statements</li>
  <li>Number of manual deployment steps</li>
  <li>Number of projects</li>
  <li>Percentage of code/projects that's "dead", as in, not referenced anywhere</li>
  <li>Number of WTF's during code reviews</li>
  <li>Total lines of code, maybe broken down by tier</li>
  </ul>