Fortunately McConnell also points out that given clear guidance, developers will actually do what they're told, which is reassuring. Setting clear goals is a pretty key management tenant, but one easily forgotten. Some of these characteristics (say performance, code-complexity) can even yeild metrics, so you can deal with the project graphically: BigVisibleCharts.
On my previous project, we used this list as the basis for our peer code reviews, out of which came the categorisation I posted previously, but to re-iterate (slightly re-worded):
- Customer Facing (most of the External Characteristics)
- Maintenance and Design (most of the Internal Characteristics)
- Defects (Just hunting for bugs)
PS: If you weren't sure what some of the characteristics meant, maybe you should re-read your copy of CodeComplete.