Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>How does bug fixing fit into your overall development philosophy? Where I work, we'll have specific times that are where bugs are our focus so we just go bug squashing at those times and somewhat ignore it the rest of the time. It isn't a perfect approach, but it is a pretty good idea.</p> <p>If you want something of the opposite end of the spectrum, I used to work somewhere that would have these daily bug triage meetings were whoever wanted to attend would come and some would pick which bugs they wanted to fix or make comments like this bug isn't that bad and can be left to a service pack project rather than fixing it for the initial release. Now, this was in a group where there were about 16 developers and the whole point seemed to be about who would work on what. It did get dropped a couple of weeks later as it didn't seem to be the best use of time for those doing it and really there were just a few managers that could handle prioritizing and assigning bugs.</p> <hr> <p>Inefficient is an understatement about the second approach if you think about how much each developer is paid and most of the time just sitting around as really there may be 1-2 developers that care enough about a bug to discuss it with QA at this meeting. I'm posting about it here because I want to warn people against having this kind of approach as it can be much easier to have managers assign the bugs and if someone wants to know what to work on, refer them to the bug tracking software. That's a simpler approach.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload