The Tester’s Story: Painting the Picture of Risk

Identifying risk by detecting bugs may be the primary goal of a tester but we have a unique responsibility within software development projects. Clearly communicating risk can mean the difference between successful mitigation and the nightmare scenario of critical revenue streams being interrupted. But no one wants to channel Chicken Little or conjure images of the boy who cried wolf every time a bug is discovered.

Critical issues must be communicated in a manner that delivers the right messages while building trust. But trust can be difficult to create given the special nature of testing and the challenges it can present in the relationship between testers and developers. Add the stakeholders into the mix and it is not always easy for testers to be heard, much less trusted. Learn how to better communicate with developers and stakeholders, build and maintain trust, and ensure issues and defects are proactively addressed by telling an effective story that paints the right picture for all parties.

Join Shaun to determine the best way to communicate your story to the relevant stakeholders and identify the risks that exist without losing trust or crying wolf. Get your voice heard in your organization.

Learning Objectives:

  • What to do when you find a bug (newsflash: it’s not only about reporting the issue)
  • Build trust when communicating with developers
  • Demonstrate risks to project stakeholders

RISK
Location: Date: April 20, 2016 Time: 10:00 am - 11:00 am hs__Shaun_Bradshaw Shaun Bradshaw