There probably is truth in metrics and metrics should be a powerful tool, but in reality there are many factors influencing the metrics we gather. When we want to evaluate a process using statistics we hope that measurable events are independent. I have already heard some discussion on the effects of design on code quality. Many other factors could be listed: maintenance vs green field, embedded vs classic application vs web-based application, language used, schedule constraints etc. If your shop supports one project or one type of project, you should get more benefit from metrics. I think Joel's perspective is evident. He owns and manages a small shop and he can directly influence quality by hiring the people he wants and directing many key factors that effect quality. And nothing still beats the classic "management by walking around". On the other end of the spectrum is management by metrics. Metrics from several varying projects are rolled up together and fed upstairs to managers who make key decisions. This is obviously ridiculous.
Flat View: This topic has 50 replies
on 51 pages
[
«
|
121314151617181920
|
»
]
Previous Topic
