developer productivity metrics

• Productivity
  
  
  
  • Does the developer get a reasonable amount of work done in a given period of time?
  
  
  • Is the developer's velocity on bug fixing sufficient?
  
  
  
  

• Engagement
  
  
  
  • Is the developer dedicated to his/her craft?
  
  
  • Is the developer committed to delivering software on time?
  
  
  • Is the developer dedicated to company success?
  
  
  
  


• Attention to Quality
  
  
  
  • To what degree does the developer's code work as designed?
  
  
  • Does the developer thoroughly test code and believe it to be correct before checking it in?
  
  
  • Do a minimal number of bugs get reported against his/her code?
  
  
  • Does the developer write unit tests for all new code?
  
  
  • Does the developer follow the Boy Scout Rule and leave a module cleaner than it was before he or she worked on it?
  
  
  
  


• Code Base Knowledge and Management
  
  
  
  • To what degree does the developer understand the code base assigned to him/her?
  
  
  • Does the developer take responsibility for his/her team's code base, improving it at every opportunity?
  
  
  
  


• Adherence to coding guidelines and techniques
  
  
  
  • Does developer's code routinely meet coding standards?
  
  
  • Do code reviews reveal a minimum of problems and discrepancies?
  
  
  • Does the developer use Dependency Injection to ensure decoupled code?
  
  
  
  


• Learning and Skills
  
  
  
  • Is the developer constantly learning and improving his/her skills?
  
  
  • Does the developer show a passion for the craft of software development?
  
  
  
  


• Personal Responsibility
  
  
  
  • Does the developer first assume that the error lies within his or her code?
  
  
  • Does the developer understand that he or she is solely responsible for their code working correctly?
  
  
  • Does the developer take pride in their code, ensuring it is clean, tested, easy to read, and easy to maintain?