tag:blogger.com,1999:blog-18334214.post7106733807279789206..comments2023-11-05T06:16:16.563-06:00Comments on Its all about Biz, man: Determine root cause of a problemUnknownnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-18334214.post-59525895352652849412009-01-28T05:37:00.000-06:002009-01-28T05:37:00.000-06:005 Whys work well when we understand the problem sp...5 Whys work well when we understand the problem space well or the problem space is simple. Otherwise, something like a fishbone diagram might be more effective. For really complex problems, Current Reality Trees may be the way to go.Jason Yiphttps://www.blogger.com/profile/08286768587936088382noreply@blogger.comtag:blogger.com,1999:blog-18334214.post-35006379210804412962009-01-26T09:52:00.000-06:002009-01-26T09:52:00.000-06:00Torbjörn I accept to what to say. I wanted to give...Torbjörn I accept to what to say. I wanted to give an example how to use 5 whys. <BR/><BR/>I really like your point "Tooling or lack-of-using-practice-x is almost never the problem, they can be the solution though." It is well put.<BR/><BR/>Thanks for your inputSiva Jagadeesanhttps://www.blogger.com/profile/04354214547479487267noreply@blogger.comtag:blogger.com,1999:blog-18334214.post-8377189556700669612009-01-26T03:21:00.000-06:002009-01-26T03:21:00.000-06:00Short and sweet but I belive that this "5 Whys" wa...Short and sweet but I belive that this "5 Whys" was written with the last two points "decided" from the start. I've seen too many exercies like this turn end with what the facilitator thought we should be doing all along or always end up with "blame management/customer". <BR/><BR/>4. Clearly identifies lack of unit tests as a cause but wouldn't a comprehensive acceptance test suite also fix the defect as this level? <BR/><BR/>Or simply concluding "development does not take responsibility for shipping bug-free code to testing". <BR/><BR/>In the later scenario we would probably end up with Jasons #7 developers don't see it as their duty to prevent defects as a root cause and hopefully that could spur a discussion amongst them. Leading to some solution to fix that, probably some sort of test automation. And there TDD could be introduced as one way to fix the problem. Tooling or lack-of-using-practice-x is almost never the problem, they can be the solution though.Torbjörn Gyllebringhttps://www.blogger.com/profile/12440238354205811138noreply@blogger.comtag:blogger.com,1999:blog-18334214.post-26038115043451151392009-01-25T00:13:00.000-06:002009-01-25T00:13:00.000-06:00Yah Jason that is another possibility. I wrote tha...Yah Jason that is another possibility. I wrote that as an example :)Siva Jagadeesanhttps://www.blogger.com/profile/04354214547479487267noreply@blogger.comtag:blogger.com,1999:blog-18334214.post-15189668730010240332009-01-24T21:10:00.000-06:002009-01-24T21:10:00.000-06:00I'd also go a different branch6. Why don't the dev...I'd also go a different branch<BR/><BR/>6. Why don't the developers do TDD or some other method to prevent defects?<BR/><BR/>- Because they don't see it as their responsibility to prevent defects<BR/><BR/>7. Why don't the developers see it as their responsibility to prevent defects?<BR/><BR/>- Because the overall team does not know the <A HREF="http://jchyip.blogspot.com/2009/01/no-matter-how-many-times-you-say-it-we.html" REL="nofollow">difference between Quality Assurance and Quality Control</A>Jason Yiphttps://www.blogger.com/profile/08286768587936088382noreply@blogger.com