So now my company is into the mid-year review season. I don't have to do these being an individual contributor (meaning I have no direct reports). But I have seen some of the suggested metrics for our IT partners, specifically software developers. I think they're ridiculously silly and not applicable to today's modern developer. What do you think?
Metric Title
- Achieve _____ % bug-free code for delivery to production.
- Decrease defect rate by _____% by (date)
- Document 100% of coding changes
- Identify application development process improvement ideas by (date)
- Increase code production rate to ___(#) lines of code per (unit of time) by (date)
- Increase mean time to failure __% by (date)
- Learn __(#) new programming languages by (date)
- Provide work estimates for programming tasks that are accurate within ___% of actuals
- Recommend new programming languages for inclusion in toolkit by (date)
- Reduce mean time to repair failures ___% by (date)
- Reduce rate of errors per lines of code ___% by (date)
I'll start - at first glance, I think there is only ONE valid metric. ALL of the others are either things you should be doing NOW at 100%, things that have ZERO impact on quality or performance (like #5), or are so dependent on environment and others as to be easily gamed (#6)
Which one is my personal favorite? #8 - Accurate estimates will reward you, your manager, and your team beyond expectations! Why? The credibility gained for being honest, accurate, and reasonable 100% of the time is extremely valuable to your clients - internal or otherwise. It means you know what you are doing, have architected an intelligent design and that you fully understand everything associated with providing a great product! It means that your clients can plan for (and count on) your delivery!
What do you think? Ready? GO!