tag:blogger.com,1999:blog-3075419760307323302.post1753074988805756386..comments2023-06-17T06:22:17.460-04:00Comments on Wunda's World: where do the bugs go?wendyhttp://www.blogger.com/profile/12983025600472588046noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3075419760307323302.post-75396064562579984462007-03-16T00:42:00.000-04:002007-03-16T00:42:00.000-04:001)Not necessarily. I've found that bugs go either ...1)Not necessarily. I've found that bugs go either way, you can or can't estimate them... And the ones you can't, you usually can after a few hours of investigation... Thats something rule "4" helps with.<BR/>2)That's what rule "5" is for :)<BR/><BR/>However, I'm not convinced non-negotiable quality, application bugs and "broken" are all relative or mutually exclusive. It really depends on the bugs, whats "broken," when you're releasing and what the customer wants.<BR/><BR/>3) Aren't you on VACATION???wendyhttps://www.blogger.com/profile/12983025600472588046noreply@blogger.comtag:blogger.com,1999:blog-3075419760307323302.post-57096509011612044722007-03-16T00:30:00.000-04:002007-03-16T00:30:00.000-04:00Questions about your suggestion:1) If something is...Questions about your suggestion:<BR/><BR/>1) If something is a bug, isn't it by nature very difficult to estimate?<BR/>2) If quality is a non-negotiable and owned by the team, isn't it wrong to put the customer in charge of deciding whether it's OK to have things broken?Anonymousnoreply@blogger.com