In my opinnion the biggest mistake one can do with metrics is to try to figure out what a single measurement result means in some universal "how good is my code" context. Measuring for measurement's sake is (almost) insane.
In order to really benefit from metrics they should be used as a part of wider QA plan with defined goals. Measure repeatedly and compare the results, not with some external magic values, but with each other, in order to see the direction the product/process is going to. Metrics don't tell so much about wether things are good or bad but more about wether something is better or worse.
It is not the easiest of tasks to set up a proper mesurement process. But in my opinnion if you don't do it the hard way, it is better not to do it at all.
Flat View: This topic has 50 replies
on 51 pages
[
«
|
91011121314151617
|
»
]
Previous Topic
