Software Best Practices

In my opinion there are two distinct topics here; "the measure" and "what you do with the measure". The Measure This is an interesting measure. It does indeed (from a mathematical point of view) have some desirable qualities. It appears to be scale invariant. That is, it would allow...

Some of the metrics we are looking at include the following: Percentage of use cases met and developer tested Percentage of requirements met and developer tested Same again but integrated No of times regression testing has passed Amount of risk remaining and its distribution Defect discovery rate and...

[quote user="MuhammadAdel"]Your method doesn't take into consideration difference in the number of lines of code produced daily[/quote] You lost me; why should that make a difference? Yes, 500 lines with 10 defective lines is the same as 1000 lines with 20 defective lines; that's what...

[quote user="MuhammadAdel"] code quality: good structured code, easy to maintain, etc. Performance of the code: developer avoids bottle necks in the programming language or the platform based on his knowledge and experience. Complexity of the code or the algorithm used. The severity of bugs...

Your method doesn't take into consideration difference in the number of lines of code produced daily. Based on what I have understood, two developers A and B , A producing 500 lines of code with 10 defects is the same as B producing 1000 lines of code with 20 defects. Your measuring method also doesn't...

I know this forum is about metrics for software projects, but I'm curious about metrics to measure the productivity of the developers themselves. Certainly this topic has been discussed a lot in the literature and I've seen applications of Function Points, Feature Points, Defects Per KLOC, etc...