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