Consultative QA as a way to empower engineering teams

Consultative QA has the ability to transform your engineering team, putting the responsibility on the engineers for the quality of their work, whilst still having a level of assurance that a seasoned tester can bring.

Many companies run one of two strategies when it comes to the quality assurance (QA) work their engineering teams produce: traditional QA and no QA. Both strategies can be seen as opposite ends of the QA spectrum, with the no QA movement (or rather, developers doing QA) being a reaction to the heavy-handed QA processes experienced in the past. Having developers being responsible for QA might work in some organizations but it depends on the level of risk you’re willing to accept.

Join LeadDev.com for free to access this content