Optimizing Your Testing Team

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 product team. Enter the Technology Enablement approach. The testing team is set up to be both a unique and key player to not only inform the team on the testing strategies of the technical solutions, but the right QE can also be influential in  the overall quality of the processes used. We will talk about three different approaches when building and maintaining a software quality team and deep-dive in to each: centralized, decentralized and hybrid
We will discuss the nimble characteristics  that belong to each approach since each has its pros and cons. We will have a thoughtful discussion on them as they pertain to hiring, skills development, and building a culture of quality first and how you can ensure QE is operating in the most efficient way.

Melissa Tondi

Melissa Tondi has spent most of her career working within software testing teams. She is the Director of Quality Engineering at Guild Education 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 test 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.