Moneyball is about baseball. But it’s also about breaking down accepted preconceptions and finding new ways to look at individual skills and how they mesh as a team. Sometimes the characteristics that we believe a team needs aren’t all that important in assessing and improving quality. It’s also about people deceiving themselves, believing something to be true because they think they experienced it. In fact, some of a team’s accepted practices may have less an impact on quality than we think. This presentation examines how to use data to tell the right story about our success in shipping high quality applications. It takes a look at some of our preconceptions about testing and individual skills. It identifies characteristics necessary to building and running a high-performance testing team. It applies the Moneyball approach to testing and quality to give teams the best bang for their buck in evaluating their own capabilities and requirements, and delivering the highest quality possible.
- Understand the dynamic of you team and its impact on improving software quality.
- Recognize your own preconceptions and biases in evaluating quality
- Know when to rely on instinct for assessing quality and when to take the time to make a deliberate and informed decision