In this episode Matthew and Federico discuss what it means to treat the QA role as a “service” rather than a “requirement”.
News
Fede has a new blog about testing. Fede to give a QA talk at Dev Connections
QA as a service
Signs that development team sees QA as a burden. Difference in QA cultures: “some else is responsible, they need to change” “influence others by changing yourself”
Think of QA as a service provider and the rest of the development team as the consumer. Strive to give as much value. Perception and reputation and why it’s important to provide value that is tangible to the rest of the team. Change the QA response from “no, we can’t do take that work”, to “how can we find something that works”. Increase awareness across the development team about what, how and why the QA team does what it does. First hand anecdotes from our team.