On Thu, Feb 4, 2010 at 06:06, Robert Casto <casto.rob...@gmail.com> wrote: > Why not bug count. Fewer bugs and the amount of time to fix them put > together should give you an idea of how productive a team is. If they have > lots of bugs or spend lots of time trying to fix them, then they are not > such a good team. If they have lots of bugs reported but they are quick to > fix, then that is not a penalty. They could do better than a team that has > few bugs but spends lots of time trying to fix them.
Why not bug count? Well, some might argue that "the number of bug reports is proportional to the number of users, not to the number of defects". http://www.rants.org/2010/01/10/bugs-users-and-tech-debt/ And if there's truth to that, what exactly would you measuring by counting bugs? // Ben -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
