Reverse Uno

Develop. Test. Repeat.

Standard development and agile processes often have a standard flow of testing to follow after development. And because of this we have developers that look after a feature during the development phase and QA's to test the feature after development is complete.

The setup works. A lot of companies have adopted it. This is why teams are a built on a dev to tester ratio. But is this the best way to go about things? I'm not so sure.

A typical workflow here would be requirements written up and passed to the development team. But here's the catch, a developer would develop code and once they completed it, it would be handed to the QA for testing.

But i've always felt like this is a dysfunctional process. It almost feels like QA's are checking code that's been written by developers. And if that's the case, who is then checking that the QA's have properly tested what's to be tested? And if a quality check only happens after development, then quality is an after thought and not something that the entire team has considered and implemented throughout the process.

Working in the QA space for over 13 years...i've seen the quality space since the waterfall era to what it is today. And I know there's a better way of doing things...and i'm determined to design a quality role and system that my peers and colleagues would be proud of.

Here's to me raising up to the challenge.