While redefining the QA function at work, I keep coming back to this question:
What is Software Quality?
If we deliver exactly what the requirements / user story says, is that quality?
We’d say that’s validation, so we must also do verification which is ‘are we building the right thing’,
The problem there is, in a large organization a bunch of ‘groups’ have to sign off.
Now the ‘end users’ (if you will) don’t align to a single version of what’s expected.
That’s why I sometimes feel developing software is not a science, it’s an art.
It’s an art to bring a vision of a select group of people to life.
The details of the vision for all might be different, but they all might be connected with a common emotion.
Therefore, in the end, it’s about answering to that shared ‘emotion’ of the stakeholders.