Just because the “Q” in “QA” stands for “Quality” doesn't mean that this role should be the only one who's responsible for making sure features are up to standards.
Unfortunately, too many QAs spend their limited time just making sure that features WORK, let alone finding edge cases and addressing actual bugs. And then they have to pull the developer back in to fix the feature after the developer has already moved on to the next one. Talk about a bottleneck!
Quality can't only be QA's job—it needs to be everyone's job. Spending the time building in quality up front will prevent overhead involved in re-work, keeping your system flowing and allowing QA to do what they're best at.
In this episode, you'll learn three actionable steps to start making quality a team sport for your software development team.