At a place I worked out there was a team that used KPIs for development. There were about 15 people on the team. They were maintaining an internal application that ran the business. Their change request / bug tracking system had fields to score the change. The score fields had to be completed by three different people; the person completed the change, the code reviewer (peer from the team) as well as the internal client who requested the change. The scores were built by combining the score in a series of categories including quality and customer service.
The change request / bug tracking system scores were used in annual reviews of individuals as well as for the team. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, 29 June 2010 10:22 AM To: [email protected] Subject: RE: KPI's for software developers Several years ago we outsourced development of several modules and got a horrible mess of spaghetti code in return. On more than one occasion we've fixed bugs purely by deleting code, without adding or changing any existing code. And refactoring parts of these modules often results in a 50% or greater reduction in the size of the code and the same functionality (except for the bugs). If I didn't know otherwise, I would have sworn they were being paid per line of code. Ben ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Corneliu I. Tusnea Sent: Monday, 28 June 2010 8:08 PM To: ozDotNet Subject: Re: KPI's for software developers >> So what about the people who delete code? I know someone who measures >> himself on lines deleted. :) >> No name, but I think its a great idea! Are you talking about me again? :) I quite often measure my success rate by number of lines re-factored (which most often mean deleted). I consider a good achievement when I reduce the codebase I'm working by about 30-40% while adding 10-15% new functionality in those areas. Corneliu. On Fri, Jun 25, 2010 at 10:51 AM, Stephen Price <[email protected]<mailto:[email protected]>> wrote: So what about the people who delete code? I know someone who measures himself on lines deleted. :) No name, but I think its a great idea! On Fri, Jun 25, 2010 at 8:44 AM, David Kean <[email protected]<mailto:[email protected]>> wrote: Definitely track it by the amount of code that write, the bugs they fix and soda they drink. ;) From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Richard Moore Sent: Thursday, June 24, 2010 5:40 PM To: [email protected]<mailto:[email protected]> Subject: KPI's for software developers Hi all Does anyone have any good useful key performance indicators (KPI) that measure a software developers performance? Kind regards Richard Moore Analyst Programmer [cid:[email protected]] Ph: +61 7 3340 2500 Fx: +61 7 3340 2550 23 Hi-Tech Court, Eight Mile Plains, Qld 4113 Locked Bag 38, Acacia Ridge, Qld 4110 This email is intended for the named recipient only. The information it contains may be confidential or commercially sensitive. If you are not the intended recipient you must not reproduce or distribute any part of this email, disclose its contents to any other party, or take any action in reliance on it. If you have received this email in error, please contact the sender immediately and delete the message from your computer.
<<inline: image001.gif>>
