WTF's/Minute is a good measure. Sorry it's Friday.
Ok ok, some serious things that could be measured would be lines of code/bugs covered in code inspections. MS exams passed. Unit tests written, percentage code covered. If there are bugs/defects, then the number of those fixed. If working agile then, number of tasks completed. It probably has to be something they are already doing now, that can be measured. No point in measuring their performance on something they are not doing (even if its something you'd like them to do). I've never liked KPI's mainly because I feel like I'm being judged and assessed. (which you are). Often a good idea to ask the person/people being measured what they think their KPI's should be. You then get a view of what they think they do in their jobs. cheers, Stephen On Fri, Jun 25, 2010 at 8:40 AM, Richard Moore < [email protected]> wrote: > Hi all > > > > Does anyone have any good useful key performance indicators (KPI) that > measure a software developers performance? > > > > Kind regards > > > > > > *Richard Moore > Analyst Programmer* > > [image: WSR-Signature.png] > > 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 > > >
<<image001.gif>>
