How about, on any piece of work have someone external make estimates of the time required. These are not revealed to the developers. If everyone is measured against those estimates, even if they are always wrong, you can at least compare developers. Obviously there will be some degree of variation in the accuracy of the estimates but it will give an idea. If developer A always takes 50% roughly longer than the estimate and developer B take 150% long it easier to see which developer is performing better.
Jeff -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of silky Sent: Friday, 25 June 2010 4:52 PM To: ozDotNet Subject: Re: KPI's for software developers On Fri, Jun 25, 2010 at 6:48 PM, James Chapman-Smith <[email protected]> wrote: [...] > If I were pressed for actually cool KPI I would suggest Ratio of Test Code to Production Code, Percentage of Code coverage & Feature Burn Rate. It shouldn't need to be pointed out that these are equally flawed (if not more so, with 'ratio of test to production'). > Cheers. > James. -- silky http://www.programmingbranch.com
