3 ms·

Those are terribly hard things to measure with metrics. Please for the love of all things beautiful may no one list out "number of bugs" as something they measu

by dlu 12y ago

Those are terribly hard things to measure with metrics. Please for the love of all things beautiful may no one list out "number of bugs" as something they measure. A lot of this gets covered in retrospectives. Making sure that you don't repeat similar mistakes over and over again and that the team is evolving rather than becoming static. I tend to focus more on how well we hit our goals (including business goals) so that will include things like, "Are we getting better at estimates?" It could also informally include, are Dev1 and Dev2 arguing less and communicating better? I usually leave metrics to the product side. Find your version of Facebook's "7 friends in 10 days"

thejteam 12y ago
Your comment about bugs reminds me of my first job. One day the senior guy sitting next to me starting cursing. The program manager emailed him and asked him, before he even started coding, to estimate how many bugs there will be in the software in one year.
Rikishei 12y ago
At my job, where I am a tester, "number of bugs" is one of the most prominent metrics in our evaluation. I have tried to talk 3 of my bosses out of that (2 of which are engineers, one of them has a masters degree in some area of computing), but to no avail. Sigh... OP: Do NOT use bug count, for all that is holy.