Do you feel like your team is under the gun to test everything when a new feature is rolled out? Do you worry that your teammates don’t understand why you choose to test the items you do? Do you feel like you can’t communicate those risks to them in a way they understand? Are there moments in your life where you deeply question if you can successfully complete the testing requirements of a sprint? If you answered yes to any of those items, this is the talk for you.
In this webinar, Senior Software Test Engineer Jenny Bramble discusses risk as a tangible metric and explains how to break it down into components that you can use to talk to developers, product owners, business people, and any other stakeholders. Having a common language of what risk is and what it’s made of allows us to decide what we should test and when we should test it – and then communicate that to our stakeholders. Jenny will also talk about how to build a risk matrix, and why we should even bother.
You will learn:
- How to best define and discuss risk as a tangible metric
- How to determine when and what you should test to effectively communicate back to stakeholders
- The importance of building a risk matrix