Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I used to analyse performance of programmers in my team by looking at the issues they have closed. Many of the issues are of course bugs. And here another important performance aspect comes - who introduced the bugs. I am wondering, if creating a custom field in the issue tracking system "Blamed" for reporting the person who generated the problem, is a good practice.

One one hand it seems ok to me to promote personal responsibility for quality and this could reduce the additional work we have due to careless programming. On the other hand this is negative, things are sometimes vague and sometimes there is a reason such us "this thing had to be done very quickly due to a client's...".

What to you think?

share|improve this question

marked as duplicate by MichaelT, whatsisname, Blrfl, FrustratedWithFormsDesigner, GlenH7 Jun 2 at 23:02

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

6  
What do you plan on doing with this information and how much of a productivity decline will you accept because no one want to ever check in a bug and will fight to the death to avoid being the one to blame. –  JeffO Jun 2 at 20:22
3  
3  
This is both a duplicate questions and a terrible idea, for reasons documented in the duped question. –  whatsisname Jun 2 at 20:37
3  
It doesn't have to be negative. Quite frankly I would be delighted to have a one on one with a colleague about a tricky bug I created. Generally human nature makes this tough. Too many people take things personally. –  ChaosPandion Jun 2 at 20:41
1  
JensG it may not be intended to be about "blame", but when the OP creates a field called 'Blame' with peoples names in it, some people tend to see the obvious: you are blaming someone. It is good to figure it out and analyze that I agree. Doing it via a field called blame does not seem a good approach imho. One alternative is to use retrospectives to review prior work. –  Michael Durrant Jun 2 at 21:43

1 Answer 1

No, no, 1024 times no

What's important is to figure out how to prevent similar future bugs. Everyone makes mistakes, there is nothing to be gained from finger-pointing. Blaming people does not improve the process, nor does it help the team

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.