Developer Grades: Where Do You Fall-in?

Bre-the-programmer

I am leading a mid size development team of 15 members. Recently I had to put grades on them to facilitate future assignments on projects. Just thought I could share those grade points, so that you have a quick asses!

 

Grades

Level

Comments

A+

Outstanding

Fully fitted for enterprise level leadership and architecture.

A

Excellent

Can be a core contributor in architecture for enterprise level projects.

B+

Very Good

Excellent implementer of the architectures for enterprise level projects defined by others. Can take leadership (architecture and management) for mid range application.

B

Good

Nice implementer for mid range projects.

C+

Satisfactory

Moderate implementer for mid range projects. Can be assigned small projects fully.

C

Better than poor

Requires a close guidance for coding tasks. Can be a good tester in code level.

D+

Poor

Not reliable for coding. Can be assigned for UI level fine tuning, technical documentation, deployment.

D

Non-satisfactory

Can't be a direct part in the team. Requires continuous training and monitoring.

Print | posted on Thursday, January 10, 2008 1:03 PM

Feedback

# re: Developer Grades: Where Do You Fall-in?

left by Paul at 1/10/2008 11:52 PM Gravatar
I'm gonna go with Joel Spolski on this one
http://www.joelonsoftware.com/articles/fog0000000073.html

Why even bother having grades C and below? Why would you want these people working for you?

C - "Requires a close guidance for coding tasks", so having this developer requires you expend another one. Just use the good developer and fire the C developer

D+ - "Not reliable for coding", again, why would you have a "developer" who is not reliable for coding. It doesn't make any sense.

D - Why is this person even allowed in the building?

If you hire anything less than "A" developers, you are doing a disservice to your company and to your customers.
Post A Comment
Title:
Name:
Email:
Comment:
Verification: