Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Scribd will begin operating the SlideShare business on September 24, 2020 As of this date, Scribd will manage your SlideShare account and any content you may have on SlideShare, and Scribd's General Terms of Use and Privacy Policy will apply. If you wish to opt out, please close your SlideShare account. Learn more.
Published on
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 team mates 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? Do you just really like cats?
If you answered yes to any of those items–this is the talk for you.
We will define and discuss risk as a tangible metric, striving 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. We will also talk about building a risk matrix and why we should even bother. Included will be a heavy dose of jokes, anecdotes, and pictures of my cats.
Be the first to comment