Do you feel like you're under the gun to test everything when your team rolls out a new feature? Do you worry that your teammates don't understand why you choose to test the items you do? 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. We will also talk about building a risk matrix and why we should even bother. Included will be a heavy dose of jokes, storytelling, anecdotes, and pictures of my cat.
- Defining the elements of risk to create a tangible metric that can be used in discussions about stories, features, projects, applications, etc
- How to start the conversation about risk and other talking points
- Creating a risk matrix
- Jenny's cat is really pretty adorable
- Elements of risk that are not always considered like user morale, social karma, and other soft metrics
What You'll Learn
Director of Quality Engineering
Jenny came up through support and DevOps, cutting her teeth on that interesting role that acts as the 'translator' between customer requests from support and the development team. Her love of support and the human side of problems lets her find a sweet spot between empathy for the user and empathy for my team.
She's done testing, support, or human interfacing for most of her career. She finds herself happiest when she's making an impact on other people--whether it's helping find issues in applications, leading scrum, speaking at events, or just grabbing a coffee and chatting.