I’m a consultant so sometimes I arrive at projects which are already ongoing for years. What I often notice is that they have a huge application with loads of bugs in the backlog. (Non-Blocking bugs)
They only solve them when the customer reports them. Most of the bugs are only solved when the customer reports them and not when a QA finds them on the test environment (only during new feature development & blocking bugs)
How do you guys deal with these backlogs? (I’ve seen backlogs of 6000+ open bugs)
I sometimes am allowed to introduce like 2h-4h-1d/week time slot to focus on bug fixing, for those that “we” do kind of feel important but a lot of these bugs are not valid anymore either (we most of the time can’t afford a QA re-checking all these bug reports). So there has to be a better way to deal with bug backlogs and I’m looking for tips & tricks here.
How would you deal with joining a new project and noticing there are 6000+ open bugs?
I guess some are not blocking at all and probably will never be noticed but is it worth then having them in our backlog as open? Do you maybe have a specific status for it like ‘won’t fix-until client notices’?
Tips & Tricks are welcome