"paul" <pa********@hotmail.com> wrote in message
news:66**************************@posting.google.c om...
I'm looking for some input on what's happening out there.
Does anyone have any programmer performance yardsticks in place?
How does management analysis your programming performance?
What works what doesn't?
Some sort of formal lines per day or whatever doesn't.
You can't measure performance in that manner.
You get a piece of work in and look into scheduling it for someone.
You need to have an understanding of what they must do.
You ( or their immediate boss or someone ) should already know about how
long it ought to take.
You agree timescale with the programmer.
Maybe he thinks of some reason it'll take more or less time.
So maybe you agree a different number.
He does it.
You walkthrough with him.
How'd he do the work, did he cut corners or do a great job or what.
You look at how long he took.
Record the two somehow.
Repeat.
After some meaningful period has passed, see how he's doing and bear in mind
how everyone is doing.
If everyone works slower than you thought then congratulate yourself on
being a genius and lower the bar a bit.
--
Regards,
Andy O'Neill
