We software people are pretty passionate about what we do and some of us are quite opinionated (guilty as charged). When it comes to building software, each of us brings our own unique perspective and when you put all those perspectives and opinions and egos and biases into the mix, you can end up with something pretty special of high quality.
Quality is often defined as “value to somebody” or “value to somebody who matters” and as per the Modern Testing Principles, the only true judge of quality is the customer but if we can’t speak directly to that “somebody who matters” or to a customer and if we are trying to encourage a whole team approach to quality, how do we agree on what quality looks like?
One approach that we use quite often to form a common view of the world is called “Priority Sliders”, an open practice library (https://openpracticelibrary.com) that facilitates conversations about relative priorities and activities.
We work with the team, including the Product Owner to set the scene before starting off with an example of a quality attribute. We then ask the team to provide other quality attributes that they believe are important given their particular context.
We might end up with something like this: