Great stuff! I particularly enjoyed reading your thoughts on UTR and DAR. I think these metrics require both team discipline and personal discipline. If there is a way to measure them, there is a way to show improvement and reward it. Motivation becomes that much more easy to inspire for teams and individuals.
I also liked your idea of reporting on non-bug load. I think that is the correct (positive) perspective on reducing volume of bugs being produced, and therefore being able to focus on new development. Sometimes bug load can be indicative of necessary improvements in some team members more than others. If so, it is my opinion that those improvements are best discussed with those team members in private.
Great stuff! I particularly enjoyed reading your thoughts on UTR and DAR. I think these metrics require both team discipline and personal discipline. If there is a way to measure them, there is a way to show improvement and reward it. Motivation becomes that much more easy to inspire for teams and individuals.
I also liked your idea of reporting on non-bug load. I think that is the correct (positive) perspective on reducing volume of bugs being produced, and therefore being able to focus on new development. Sometimes bug load can be indicative of necessary improvements in some team members more than others. If so, it is my opinion that those improvements are best discussed with those team members in private.
Thanks for another great article!
Thanks Vaughn! Under-the-radar is my favorite underutilized metric that most people ignore.