I figured it out.. the first and most important KPI for software quality..<\/p>\n

Can you guess?.
\n.
\nTime from ‘prioritizing a feature’ to the time it is ‘ready for deployment’ in production.<\/p>\n

Now some might say testers don\u2019t have control over the whole process, that is true but we should be working to develop that maturity<\/p>\n

Or we might say time to market is not as important as quality of the product,<\/p>\n

My answer would be \u2013 Quality is subjective, best to get feedback from people spending money determine quality<\/p>\n

That does not mean we ship crappy stuff, some things are no brainier, seeing exceptions, basic functionality not working are obvious<\/p>\n

The part which is subjective is, certain features we might feel are very helpful, or as the user expected and therefore give the product a higher quality,<\/p>\n

In the end customer\u2019s experience, they might see that as a hindrance in using the product and would have a different perspective of the level of quality here<\/p>\n

So, anyone working towards developing software (including testers), the foremost measure should be: How quickly we can go from ideation to deployment.<\/p>\n

Thoughts?<\/p>\n

#QsDaily #testingmetrics #transformation<\/p>\n<\/div>