3 ms·
A couple of years ago we did "Bug Bankruptcy" at my old gig. We then instituted a policy: either a bug was worth fixing RIGHT NOW (or reasonably close to it, sa
by MattRogish 14y ago
A couple of years ago we did "Bug Bankruptcy" at my old gig. We then instituted a policy: either a bug was worth fixing RIGHT NOW (or reasonably close to it, say after you finish working on your feature) or NEVER. Bugs that were re-reported by users we would move up our mental immediacy list. I like it because it didn't require a fancy software solution - just the group memory. It worked really, really well, and we continue to use it today.
- jpadkins 14y agoYou didn't actually lean out the process, you just pushed more work on to a different group of people. Did people pay for this software? I can't imagine buying software that makes me find/submit bug reports and then on top of that re-submit them to actually get them fixed....
- MattRogish 14y agoNot every bug is worth fixing. But, I'd probably guess that 9x% of user-reported bugs are of the "this needs immediate fixing" variety. A lot of other bugs, mostly entered by QA and other folks in the company, fall into the "WONTFIX" bucket.
- derefr 14y ago> I can't imagine buying software that makes me find/submit bug reports and then on top of that re-submit them to actually get them fixed.... This is what pretty much all consumer infrastructure service providers rely on, though. One guy reports that his internet is out? Probably his fault. Ten people in the same area call in to complain in a one-hour period? Probably yours.