Member-only story
We are all familiar with the concept of “One Team”. We may have experienced that moment when product, engineering, and operations were united towards a common goal. That is great until we face diverging actions.
Imagine discovering a software engineer that preferred to optimize his code rather than deliver the defined user priorities. From his perspective he’s right: “For me (only), it was important”.
Succeeding at the implementation of the whole-team approach to quality results from the combination of key elements. In this article, we identify the difficulties of a “One Quality, One Team” approach sharing implémentation guidance for each point:
- A Quality not understood must be collaboratively aligned
- A Quality seen as “yet another priority” must be embedded
- A Quality that is not a personal priority must become one
- A Quality in silo must be spread organizationally
Join the QE Unit to be part of the Quality Engineering community to access regular and exclusive community content.
A Quality not understood must be collaboratively aligned
The collaboration of team members starts with a shared understanding of their roles towards a common…
