tag:blogger.com,1999:blog-8355307424351887658.post8881993164679051948..comments2021-06-28T22:46:44.499+02:00Comments on Test and Tech: Why do we test? - A bit more on the subjectOlahttp://www.blogger.com/profile/12679909077391510827noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8355307424351887658.post-71131623950990647312012-01-31T10:32:50.932+01:002012-01-31T10:32:50.932+01:00Roland, I think cutting cost and saving time has c...Roland, I think cutting cost and saving time has cost a lot of money and time in many projects. I'm sure you've seen that result to :)<br />I think that your idea about going for "what's in it for me?" is perhaps cynical but could be a very powerful move, in the right circumstances. It's about recognizing when you have to hit that switch and I have seen PM's and other stakeholders with power that might have responded to such an argument. Basically what you suggest is a version of the contract between tester and developer that James Bach is using. It's on his blog and it's a very useful list of what a tester provides. <br /><br />It's hard to convince people with one argument so I don't think that there's an easy answer or a silver bullet in this area either. My cynical side says that for some people you will be able to use the same argument every time. That's for the people that once they buy the argument they will never question it. Not my favorite kind og people :) but I know they exist.<br /><br />I have already put you on my list of people to talk to about this in order to gather experiences and develop ideas!Olahttps://www.blogger.com/profile/12679909077391510827noreply@blogger.comtag:blogger.com,1999:blog-8355307424351887658.post-32811909927612790122012-01-30T15:45:29.367+01:002012-01-30T15:45:29.367+01:00Ola,
The subject of cutting costs and time by dec...Ola, <br />The subject of cutting costs and time by decreasing test activities turns up in far too many big and expensive projects. As you write it is an educational issue, but most of the time it is too late to change the views of PM's and sponsors.<br />As Test Lead or Test Manager you wish you had some proven arguments that strikes the right chord even with the most ignorant PM, and hopefully your coming bestseller will give us a clue.<br />One idea could be to try it using a "what's in it for me* approach, where we explain to the PM that he (mostly) personally has to gain by instantly pulling his head out of the sand. <br />Maybe: "A successful project delivered to satisfied customers will be good for your career and will promote you to lead even bigger and more important projects in the future." (... even if they get the system a wee bit later)<br />Or "You are main responsible for the quality. Do you actually dare to put your reputation as PM at risk by implementing this solution in Production without knowing anything at all regarding the software quality?".<br /><br />Anyone having any better and more convincing mind-changing arguments, that can turn around a decision from one day to another?Roland Matssonnoreply@blogger.com