Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Communicating risk because you can't test everything tricentis

132 views

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.

Published in: Technology
  • Be the first to comment

Communicating risk because you can't test everything tricentis

  1. 1. COMMUNICATING RISK @jennydoesthings BECAUSE YOU CAN’T TEST EVERYTHING
  2. 2. @JENNYDOESTHINGS HI, I’M JENNY! I’m currently a Software Test Creature Engineer! ‣ History: ‣ Support —> Devops —> Support again —> QA/Support —> QA ‣ Willowtree Apps is home ‣ Enjoys cats, cupcakes, computers. ‣ jenny.bramble@gmail.com ‣ @jennydoesthings ‣ Pronouns: she/her Enough about me. Let’s talk about RISK. 2
  3. 3. HE TRAPPED HIMSELF IN THE BATHROOM FOR 12 HOURS ONCE. THIS IS DANTE. @jennydoesthings
  4. 4. @JENNYDOESTHINGS AGENDA ▸What is my job? ▸Words are terrible! ▸Defining risk ▸Using that definition ▸Talking about risk ▸Additional pictures of cats 4
  5. 5. PLEASE DON’T ASK ME TO TEST EVERYTHING I CAN’T TEST EVERYTHING @jennydoesthings
  6. 6. DANTE LIKES NICE THINGS; DON’T QUIT YOUR JOB DANTE THOUGHT THAT WAS YOUR JOB @jennydoesthings
  7. 7. THEN WHAT IS? IF TESTING EVERYTHING ISN’T MY JOB @jennydoesthings
  8. 8. @JENNYDOESTHINGS WHAT IS MY JOB? ▸Ask questions. Absorb answers. Translate them. ▸Verify that systems under test preform in the ways that all the stakeholders expect, or help reset those expectations ▸Educate other humans about ‘testing’ ▸Advocate for practices, methodologies, and thought patterns that encourage quality in the code base and the organization ▸Defuse bombs ▸Evaluate and communicate risk 8
  9. 9. FEEDING DANTE DANTE THINKS YOUR JOB ALSO ENTAILS @jennydoesthings
  10. 10. COMMUNICATION MY JOB COMES DOWN TO ONE THING @jennydoesthings
  11. 11. RISK ONE OF THE MAIN THINGS I COMMUNICATE @jennydoesthings
  12. 12. RIGHT? EVERYONE KNOWS WHAT RISK IS @jennydoesthings
  13. 13. I LIKE MY COFFEE SWEET MY SISTER LIKES HER COFFEE SWEET @jennydoesthings
  14. 14. NOW HE’S QUESTIONING EVERYTHING DANTE THOUGHT HE KNEW @jennydoesthings
  15. 15. WORDS ARE THE WORST WAY TO COMMUNICATE WHEN IT COMES DOWN TO IT @jennydoesthings
  16. 16. AND MAKE THEM MEANINGFUL BUT WE CAN MAKE THEM BETTER @jennydoesthings
  17. 17. @JENNYDOESTHINGS WORDS ARE THE WORST WAY TO COMMUNICATE BUT… ▸Defining terms lets us communicate across cross-functional teams ▸Using the same words AND meanings ▸It gives us an ability to justify our decisions to people outside our sphere ▸Give updates that have depth ▸Help determine what resources we need to apply to a project 17
  18. 18. BECAUSE WE ALL KNOW WHAT WE’RE TALKING ABOUT WE CAN NOW COMMUNICATE MORE CLEARLY AND PRECISELY @jennydoesthings
  19. 19. WITH BITING (AND SOME CRYING) DANTE EXCLUSIVELY COMMUNICATES @jennydoesthings
  20. 20. @JENNYDOESTHINGS WHAT IS RISK? ▸ Anything that can go wrong ▸ Something awful ▸ A scary situation ▸ A headline bug ▸ Running out of cat food ▸ EVERYBODY PANIC ▸ PRODUCTION IS DOWN ▸ WE ARE ALL GOING TO GET FIRED 20
  21. 21. RISK THE IMPACT OF FAILURE THE PROBABILITY THAT FAILURE WILL OCCUR @jennydoesthings
  22. 22. AND HE WOULD LIKE TO KNOW MORE THIS INTERESTS DANTE @jennydoesthings
  23. 23. IMPACT OF ANY POTENTIAL NEGATIVE IMPACT CONTRIBUTES TO THE RISK OF AN APPLICATION OR FEATURE @jennydoesthings
  24. 24. @JENNYDOESTHINGS IMPACT OF FAILURE ‣ Technical ‣ Loss of data ‣ Introduction of security flaws ‣ Business ‣ Revenue cannot be collected ‣ Critical functions cannot be performed ‣ Morale ‣ Users have to utilize workarounds ‣ Slowed workflows ‣ Utilization of pitchforks and torches 24
  25. 25. IMPACT OF WHAT’S IMPACTFUL TO THE COMPANY? @jennydoesthings
  26. 26. THE IMPACT OF LEAVING HIM FOR THE WEEKEND IS EVERYTHING “FALLS” OFF THE TABLE. DANTE GETS IT @jennydoesthings
  27. 27. PROBABILITY OF FAILURE THE LIKELIHOOD THAT THE APPLICATION, FEATURE, OR USE CASE WILL FAIL @jennydoesthings
  28. 28. @JENNYDOESTHINGS PROBABILITY OF FAILURE ▸Has this failed before? ▸Has something similar failed before? ▸Historical data tells you about past failure ▸Defects ▸Tribal knowledge ▸QCA/RCA ▸That person that’s been here forever and knows everything 28
  29. 29. @JENNYDOESTHINGS PROBABILITY OF FAILURE ▸What features do users interact with the most? ▸How do they interact with these features? ▸What’s inherently fragile about our code base? ▸Are there external changes to consider? ▸How do you feel about it? ▸Are you proud of the feature? 29
  30. 30. PROBABILITY OF FAILURE THESE ARE VERY EDUCATED GUESSES ABOUT WHAT MIGHT FAIL @jennydoesthings
  31. 31. JUMPING OFF THE ROOF HAS A LOT OF RISK. DANTE IS PRETTY SURE @jennydoesthings
  32. 32. OTHER TYPES OF RISK FACTORS OUTSIDE OF YOUR FEATURE, USE CASE, OR APPLICATION @jennydoesthings
  33. 33. @JENNYDOESTHINGS OTHER TYPES OF RISKS ‣ Modified time table ‣ Environment issues ‣ New or inexperienced team members ‣ Natural disasters ‣ Sickness ‣ Outside pressure ‣ Industry-specific risks 33
  34. 34. IS IT REALLY NECESSARY? DANTE FEELS THAT’S A LOT TO THINK ABOUT. @jennydoesthings
  35. 35. WE CAN’T TEST EVERYTHING WE HAVE LIMITED TIME, BODIES, ATTENTION, MONEY, AND OTHER RESOURCES @jennydoesthings
  36. 36. COMMUNICATE CLEARLY AND PRECISELY WHY WE TEST WHAT WE TEST WHAT WE CAN DO IS @jennydoesthings
  37. 37. @JENNYDOESTHINGS AND WHEN I SAY “TEST”, I MEAN… ▸Giving more attention to one item than another ▸Raising concerns about a feature ▸Discussing the need for more resources ▸Choosing what stories to play ▸Asking for more time on a project ▸Manual and automated testing efforts 37
  38. 38. A SERIOUS DISCUSSION ABOUT RISK DANTE THINKS WE SHOULD HAVE @jennydoesthings
  39. 39. DANTE JUST WANTS TO TAKE NAPS HAHA, NAAAAAH @jennydoesthings
  40. 40. REAL WORLD EXAMPLE HOW DO WE TELL THE STORY OF A PROJECT ON THE RAILS? @jennydoesthings
  41. 41. @JENNYDOESTHINGS REAL WORLD EXAMPLE ▸We were able to describe the project in terms of risks and effects. ▸Risk to the user (of catastrophic failure) ▸Risk to engineering (of technical debt) ▸Risk to the team (of failing sprints) ▸When we could fix specific issues (before or after release to production) ▸I also argued for a ‘pitchfork index.’ 41
  42. 42. REAL WORLD EXAMPLE OUR CONVERSATION TURNED INTO ACTION, GAINING EXTRA TIME TO HARDEN THE PRODUCT. @jennydoesthings
  43. 43. YES: RISK MATRIX CAN WE MAKE THIS EASIER VISUALLY? @jennydoesthings
  44. 44. DO MATH FIRST THINGS FIRST @jennydoesthings
  45. 45. THERE WASN’T GOING TO BE MATH DANTE THOUGHT @jennydoesthings
  46. 46. WHAT IT IS DOESN’T MATTER AS LONG AS IT MAKES SENSE DETERMINE A RATING SYSTEM @jennydoesthings
  47. 47. MAKE A RISK MATRIX NOW, DOCUMENT IT @jennydoesthings
  48. 48. Item/Story/Use Case Impact of Failure Probability of Failure Risk Upload a song to your account 10 4 40 Set a song to “fans only” 6 8 48 Add lyrics for a song 2 3 6 @jennydoesthings
  49. 49. @JENNYDOESTHINGS OTHER ELEMENTS OF A RISK MATRIX ‣ You can include a breakdown of the types of risk if it’s hard to pull out one number ‣ Usage ‣ Fragility ‣ Merges ‣ Environmental issues ‣ User frustration ‣ User familiarity ‣ Risks may also vary depending on the phase of the project and environment 49
  50. 50. RISK MATRIX COMPLEX OR SIMPLE, AS LONG AS IT CONVEYS THE CORRECT INFORMATION @jennydoesthings
  51. 51. WITH EVERYONE INVOLVED DANTE DISCUSSES RISK @jennydoesthings
  52. 52. NO FRIENDS WERE HARMED IN THE MAKING OF THIS PRESENTATION @jennydoesthings
  53. 53. WE CAN BECOME A BETTER, MORE COHESIVE TEAM THE MORE WE TALK ABOUT RISK @jennydoesthings
  54. 54. HOW DOES THIS HELP US? WE CAN USE RISK FOR MORE THOUGHTFUL TESTING AND CONVERSATIONS @jennydoesthings
  55. 55. HOW DOES THIS HELP US? WE CAN USE RISK FOR MORE THOUGHTFUL TESTING AND CONVERSATIONS @jennydoesthings
  56. 56. THINKING ABOUT RISK DANTE SOMETIMES GETS OVERWHELMED @jennydoesthings
  57. 57. DANTE GETS OVERWHELMED A LOT TO BE FAIR @jennydoesthings
  58. 58. @JENNYDOESTHINGS AGENDA ▸What is my job? ▸Words are terrible! ▸Defining risk ▸Using that definition ▸Risk matrix and examples ▸Talking about risk ▸Additional pictures of cats 58
  59. 59. @JENNYDOESTHINGS CONVERSATION STARTERS ▸ How do you define risk? ▸ How do you tell the story of your application, feature, or use case? ▸ What’s your job title? Your job? ▸ In retrospect, when should you have spoken up? What resources do you need to make that easier next time? ▸ What takes a lot of your time at work? ▸ Sometimes, it takes a lot of “spoons” to start these conversations. Be kind and soft, like Dante. 59
  60. 60. @jennydoesthings
  61. 61. @jennydoesthings

×