@eviltester
Alan Richardson
@eviltester · 4:44

collective responsibility - why did you not find that bug?

article image placeholderUploaded by @eviltester
Why did you case you protect yourself and many of the old techniques for software testing management are about protecting yourself, creating upfront documentation that can be reviewed, identifying the scope of front. Now hopefully we move towards more collective responsibility but use the response to that question why did you not find that bug as a guide for are you working environment collective collective responsibility why did you then respond appropriately

how to deal with the question in software testing and developmenta about bugs slipping through the net

@sudha
Sudha Varadarajan
@sudha · 1:00
Allen, I have just one suggestion that I have found has worked for me and that is to have an organization structure where a product is part of the QA process. Right. So when QA is handled by their and product teams, and all three teams during the release QA cycle are part of the process, aware of all the open issues, are part of the daily bug triage, and collectively sign off on a particular relief. I think the blame kind of goes away for the most part
0:00
0:00