tag:blogger.com,1999:blog-2314019614094721290.post3979918862601524869..comments2024-03-14T10:01:57.521+01:00Comments on Common Test Sense: Introducing proper defect managementMike Meurshttp://www.blogger.com/profile/15184386727383901043noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2314019614094721290.post-58421340679224418642012-11-20T21:22:26.336+01:002012-11-20T21:22:26.336+01:00Hi Dodgedog,
Thanks for your comment.
I posted a ...Hi Dodgedog,<br /><br />Thanks for your comment.<br />I posted a new blog post to address your question. I hope it helps.<br /><br />http://commontestsense.blogspot.be/2012/11/an-example-of-simple-defect-life-cycle.html<br /> Mike Meurshttps://www.blogger.com/profile/15184386727383901043noreply@blogger.comtag:blogger.com,1999:blog-2314019614094721290.post-6017874357971383422012-11-17T13:22:43.144+01:002012-11-17T13:22:43.144+01:00I'm curious about variations in implementation...I'm curious about variations in implementation of what you say between small (<20 emp.), medium (20-70) and large (70+) companies. Whereas small companies need a compact and lightweight system, I suppose large companies put more value in clarity and assignment of responsability?<br /><br />I think it would be very useful to have a visual diagram of a "default" defect logging framework you propose (ie defects, their parameters, possible statuses, possible status flows, ...). That would make it more concrete, easier to understand and more ready to actually put into practise after reading this post.<br /><br />I think I agree on most of what you say, but for a person who does not deal with defect management on a daily basis, it is difficult to fully comprehend.Anonymoushttps://www.blogger.com/profile/02636788895133237894noreply@blogger.com