Posted by IN / 1 response

Risk Assessment

15 August 2016

My clients –Product Owners– have the right to determine acceptable level of risk for the application

Who else would?

Risk Assessment
How often, as testers, do we find ourselves arguing adamantly about a certain test or piece of functionality? It needs more testing. I don’t think it works. Why can’t we spend more time to get it right?

How often do we find ourselves emotionally involved in a defect?

Is it because we’re the ones responsible for the quality of the product? Are we the ones that are accountable for it too? Is responsibility and accountability something we are assigned? Or something we assume? Accountable to whom?

If you’re both responsible for quality and assume accountability to the end user, it becomes terribly easy to get wrapped up in squabbles about defects. But what if there is another way?

What if the Product Owner and Stakeholders are the ones testers are accountable too? Then our job is not to defend the user against defects, it’s to provide the these folks with accurate assessment of the state of the product.

Let them make the decision about the risk they are willing to accept.

 

This is an expansion of my Beliefs on Testing post. Please take a look and let me know your thoughts in the comments!

About the Author

Paul Merrill

Paul Merrill is Principal Software Engineer in Test and Founder of Beaufort Fairmont Automated Testing Services. Paul works with clients every day to accelerate testing, reduce risk, and to increase the efficacy of testing processes. You’re Agile, but is your Testing Agile? An entrepreneur, tester, and software engineer, Paul has a unique perspective on launching and maintaining quality products. He also hosts Reflection as a Service, a podcast about software development and entrepreneurship. Follow Paul on Twitter @dpaulmerrill.

one response to Risk Assessment

Leave a Reply

Your email address will not be published. Required fields are marked *