Mark Hack
  • Home
  • Blog
  • Photos

Programmer Productivity Metrics

11/24/2013

1 Comment

 
All of the process improvement processes are a variation on:
  • Define
  • Measure
  • Analyze
  • Act
  • Control
So to improve, one must measure and one of the most requested and hotly debated metrics is programmer productivity, which is used for ratings, raises and a plethora of non-process activities.

Unfortunately, this measurement is often subject to inversion ( does not correlate well to what is being measured) and when people realize that it is being used for rating, can and will be gamed. The other unfortunate reality is the programmer productivity is actually a better measurement of the process than of the people, so it is a very useful metric if used correctly.

As always, be careful what you measure since this will often be counterproductive and drive unintended consequences as can be seen in the much quoted Dilbert cartoon -
http://dilbert.com/strips/comic/1995-11-13/

In conclusion, ensure that metrics are judiciously used and that productivity and performance are based on more than one metric



1 Comment
Meloxicam link
7/21/2015 07:56:01 am

You made some decent points there. I looked on the web for additional information about the issue and found most people will go along with your views on this web site.

Reply



Leave a Reply.

    Author

    I have been in the IT industry for many years and many roles. I really enjoy learning something new every day, even if it is a new twist on an old theme

    Archives

    February 2015
    May 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013

    Categories

    All
    Organization
    Random Thoughts
    Technology

    RSS Feed

© Mark Hack 2013-2014