tag:blogger.com,1999:blog-8951904624959546499.post529405653990501858..comments2009-02-18T13:01:52.045-05:00Eric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8951904624959546499.post-18156266124312386792009-02-18T08:25:00.000-05:002009-02-18T08:25:00.000-05:00Well, I feel blame game is for week individuals. as a whole team every one is responsible for everything happened in the project.<BR/>Person should be able to take the initiative to resolve the problem.Tarik Shethhttp://www.blogger.com/profile/05658126633373504829noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-88941890378961321342009-02-13T12:59:00.000-05:002009-02-13T12:59:00.000-05:00One of the first thoughts that occurred to me was that it is possible that the tester and spec author KNEW the user's expectation, and the spec was never updated due to a myriad of reasons. This happens a lot at my company, and can be manageable at first, but eventually the documentation needs to get updated otherwise someone who wasn't part of the "nod and wink" will write up another bug or possibly in this place, just "fix" it.Joe Harternoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-64684644435385291542009-02-12T12:56:00.000-05:002009-02-12T12:56:00.000-05:00True that!<BR/><BR/>Bad apples emerge on their own. So do heros.Eric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-82246540999997113282009-02-12T01:42:00.000-05:002009-02-12T01:42:00.000-05:00I hate playing the blame game... especially during crunch time. At that point, whose fault it actually is matters very little. What matters is what can be done to resolve the problem.Green2noreply@blogger.com