The team is responsible for the quality of the product

State of mind

Not just the testers

State of mind
Agility Maturity Cards > State of mind
The team is responsible for the quality of the product

Product quality and team organisation

In a Waterfall-like organization, quality is delegated to Testers while Developers build the product on their own. As a result, Testers are the owners of the green light to production. Unfortunately, this leads to a situation where quality depends only on few people while 

  • Developers may outnumber Testers 
  • Developers generate unintentionally (hopefully!) a lot of bugs and a lot of them are left over, even when they care about quality [Sandu 2018]

Not only Developers leave some bugs in their artifacts, every actor in the whole Software Development Life Cycle (SDLC) generate them during each activity [Beizer 1994] [Moustier 2019-1]:

The SDLC can be seen as a stack of swiss cheese slices with holes that let bugs go to production [Reason 2006], each slice being a testing opportunity with their own flaws [McConnell 2004] [Moustier 2019-1]:

Moreover, it also appears that a collective approach on testing is much more efficient [Ferguson 01-2017] [Moustier 2019-1]:

These figures lead to a simple conclusion: 

Quality is everyone’s responsibility” - W. Edward Deming

Impact of product quality on the testing maturity

Testing is not something to be done alone and collaboration facilitated by a Ubiquitous Language improves testing efficiency. It also prevents fallacies from cognitive biases [Stevenson 2016] [Moustier 2019-1]. This is notably why 3 Amigos or Example Mapping are so efficient. Moreover, involving everyone in testing should not only cluster people in their own competence silo to limit WIP, this why T-Shape people are so important.

To ease collaboration around testing should also be done with built-in quality [SAFe 2021-26][SAFe 2021-27], notably thanks to testability from the Backlog to every component and knowledge sharing notably through Communities of Practice and more widely a PanTesting approach.

Agilitest’s standpoint on this practice

Since Agilitest is easy to learn because of the #nocode approach [Forsyth 2021], the use of automation testing can be spread to any kind of actor of the SDLC. This reduces the silo effect on automation.

However, automation should not be the only testing strategy to apply. As seen above, different testing techniques should be combined to chase bugs and leave no stone unturned.

To discover the whole set of practices, click here.

To go further

  • [McConnell 2004] : Steve McConnell - « Code Complete - a practical handbook of software construction » - Microsoft Press - 2004 - ISBN 0-7356-1967-0
  • [Moustier 2019-1] : Christophe Moustier – JUN 2019 – « Le test en mode agile » - ISBN 978-2-409-01943-2

© Christophe Moustier - 2021