All engineering teams should be nimble, and your testing team is no exception. In this current climate, it's even more important to ensure that test engineers are as optimized as possible in order to quickly pivot to best support and enable the delivery efforts of the development. Although sometimes overlooked, the testing team can be a key component to not only inform the teams on quality of the technical solutions, the right people can also be influential in the overall quality of the SDLC. In this session, we will talk about three different approaches when building and maintaining a software quality team - centralized, de-centralized and hybrid and how each has its own nimble characteristics Whichever approach you are taking on your testing team, each has its pros and cons and we will have a thoughtful discussion on them as they pertain to hiring, assessing overall testing and quality, and how you can ensure the team is operating in the most efficient way possible.

Meet your Speaker - Melissa Tondi:
Melissa Tondi has spent most of her career working within software testing teams. She is a frequent speaker and writer at forums focusing on the Agile, QA/QE, and DevOps spaces and is in Quality Engineering leadership and a Principal Consultant at Disrupt Testing, where she assists companies to continuously improve the pursuit of quality software—from design to delivery and everything in between. In her software testing and quality engineering careers, Melissa has focused on building and organizing teams around three major tenets—efficiency, innovation, and culture – and uses the Greatest Common Denominator (GCD) approach for determining ways in which team members can assess, implement and report on day to day activities so the gap between need and value is as small as possible.