Java programmer production

[TitanRebel <TitanRebel@xxxxxxxxxxx>]

I am a Team Leader for a small group of Java programmers (5) in an 
iSeries shop. My company is changing the employee review process. 
Employee and Manager/Team Leader will establish goals to be met for the 
upcomming year. Then at the end of the year the employee will be given a 
review and compensation based on the established goals. Sounds simple. 
However, upper management wants quantifiable goals. Goals that can be 
measured with a great degree of accuracy. I am having a hard time 
comming up with ideas. Do any of you have this sort of system? 
Experience with any sort of quantitative programmer review process would 
be great. Have any of you tried it, and have it fail?

Everything that I have thought of seems to have a problem...
Lines of code -- I'd rather have 10 lines that work, than 100 that may 
or may not!
Number of enhancements/bug fixes -- Is there really an average size bug? 
enhancement? Some are much larger and more extensive than others.

Any suggestions would be great! Obviously, this is not a specific 
problem to Java. Our RPG programmers/managers are having the same questions.

Thanks.

P.S. I know someone will ask what the process was before... It was up to 
the employee's immediate Team Leader/Manager as to what the employee's 
performance was during the year. Purely subjective. In case you are 
wondering why... two words... Compensation Consultant.