4 ms·
with no data or experience to back this up, i'd expect this to be kind of a long tail, where some will take an hour, and the majority will take 30 sec
by abacadaba 7y ago
with no data or experience to back this up, i'd expect this to be kind of a long tail, where some will take an hour, and the majority will take 30 sec
- shoes_for_thee 7y agohaving data and experience to back this up -- you are entirely correct.
- windowsworkstoo 7y agoYep, this is spot on - I used to work on a webhosting help desk and could bang out about 100 tickets a shift, because so many were small queries that required no depth work.
- klank 7y agoOld MSFT rule of thumbs was 2 bugs per day during bug crunch mode. Sounds crazy, but when you consider the number of "this text is wrong" and "that text box is too short" bugs that existed after a year of furious development, it wasn't too hard to achieve. Gotta hit that ZBB!
- mooreds 7y agoPer day? Or per hour?
- jdsully 7y agoDay. Of course some bugs would be: “this entire feature is done wrong and doesn’t work”.
- jdsully 7y agoBrought back memories. I think it might be a little Stockholm syndrome but there was just something about the pressure of getting a release out when you know it only happens once every few years. Bug triage definitely improved my persuasion technique. Now its just "meh, we'll fix it in next months release".
- bitexploder 7y agoAgile bug fix workflow ;)