tag:blogger.com,1999:blog-6005334108330583722.post2511342467576153804..comments2010-01-10T11:52:59.626-05:00Comments on Confessions of a Passionate Tester: It's still a *bug*, and your denial does not chang...Dawnhttp://www.blogger.com/profile/00149191486108175617noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6005334108330583722.post-49784120953748836832010-01-10T11:52:59.626-05:002010-01-10T11:52:59.626-05:00Arent' we trying to deliver working software? Your...Arent' we trying to deliver <b>working software</b>? Your problem description just does not fit into the definition of <i>working</i>. <br /><br />To me it sounds like that there's a plenty of culture of blame. Otherwise there wouldn't be the need for avoiding responsibility.AngryPoodlehttp://www.blogger.com/profile/09634027520929520051noreply@blogger.comtag:blogger.com,1999:blog-6005334108330583722.post-22783301098712130282010-01-06T09:15:09.836-05:002010-01-06T09:15:09.836-05:00Take a bug colored and a feature colored index car...Take a bug colored and a feature colored index card, cut them in half, and tape two different colored halves together. Write the task on that card. Don't forget the ':P'Angushttp://www.blogger.com/profile/12749636856451303702noreply@blogger.comtag:blogger.com,1999:blog-6005334108330583722.post-75460457435060163332009-11-15T21:21:38.837-05:002009-11-15T21:21:38.837-05:00ugh, with apologies to Lanette, I really hate the ...ugh, with apologies to Lanette, I really hate the "not a bug, it's a requirements problem" - seriously, this is why we need to stop looking at things from a waterfall view of the world. We are a team that works together to design & deliver software.<br /><br />That software either works for the customers and makes them delighted, or it does not. If it doesn't, it's a problem, whatever you want to call it.<br /><br />Sorry to hear your frustration - I feel for you!abbyhttp://www.blogger.com/profile/14805958673888992905noreply@blogger.comtag:blogger.com,1999:blog-6005334108330583722.post-75167966536870013332009-11-14T11:36:54.473-05:002009-11-14T11:36:54.473-05:00Michael Bolton taught me to continuously keep on a...Michael Bolton taught me to continuously keep on asking "Problem or not a problem?" In your case I would perfectly claim that you got a problem (installation not working), your developers got a problem (need to pinpoint bug to be based on a faulty installation) and your project manager (may we ship this?).<br /><br />Another thing I noticed during the last paragraph. Weinberg claims to distinguish between the origin of a failure (requirements in your case?) and the place where the error shall be fixed. This is not necessarily the same. For reasons of work-arounds it may be appropriate to change the documentation to be able to mark a bug as a feature - though I never ran into a situation where this was the outcome.Markus Gärtnerhttp://www.blogger.com/profile/15728306418553053255noreply@blogger.comtag:blogger.com,1999:blog-6005334108330583722.post-87504082880423524172009-11-13T21:57:05.878-05:002009-11-13T21:57:05.878-05:00I think you've hit this on the head. It's a (seri...I think you've hit this on the head. It's a (serious) bug to silently fail to install correctly. As you imply by your last paragraph, the semantic argument about how to classify the problem (whether to use the term "bug" or not) isn't really a useful activity.<br /><br />Even assuming (for example) that the failure was due to a third party installation mechanism, there's a quote that applies here: "Just because it is not your fault does not mean it is not your problem."DThttp://www.blogger.com/profile/05886757453212013843noreply@blogger.com