Discussion Locked

Developing Metrics for Developers

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've read some of the comments to an earlier question about measuring performance but they only hit the surface of things I already know about: you want to measure efficiency, effectiveness, customer service, etc.
I need to develop metrics for developers but measure what? Lines of code, number of bugs found, number of webpages or subroutines developed, etc? Those aren't good since it varies greatly with language used, tools used, complexity, etc. What SPECIFIC metrics can be developed to measure quality, efficiency, and effectiveness of my web developers?

1 reply

by james r linn

...that lines of code subroutines etc. are a poor metric as they are not an "apples to apples" comparison unless everyone is doing the same thing.

What I like to use, for developers and others, is the person's ability to set and meet realisic deadlines. We all know that most projects slip their deadlines, but there are major differences between slips of days and slips of months.

Measure the percentage of completion to estimate. It may be that some of your best developers are the worst atestimating - so this is best looked at a baseline for individuals , not a way to judge one developer against another.

For testing ability - how many bugs are missed in unit and system testing and found in user testing.

For other measures you might want to come up with a way of having "catagories" for different levels of application complexity - at leats that way you can do some measurement of how different project stack up against each other.

James

This discussion is closed to new replies.