Member-only story
Break down traditional QA silos and empower developers to own quality checks.
“Ready for testing” is a phrase thrown around the space of tight-knit software development teams. And it generally signals the turning point from which a bunch of code, representing a feature has reached a state where a developer perceives the feature as “ready for testing”.
From this point on we look to our fellow QA, dust our hands off the feature, take a well deserved break and move on to the next feature in sight.
And it looks a little like this:
But more often than not, the reality is more like this:
For many software teams, this posseses a big problem, and quite often the QA is faced with having to absorb, manage and perform testing.
If your team is like the majority of teams, then as a result, you’ll eventually experience and run into timely delays, halted releases and a sea of questions from all directions asking when we can expect to release.
A company may eventually get restless and expand the budget allowing to hire more QA’s: the delays we knew begin to vanish…
