30 Days of Quality Day 9: Discussion about "Quality"

Contribute to a discussion about “quality”

I’d like to understand the mindset for asserting that an application or a service meets a customer perceived value of quality as I find it hard to establish a baseline for it.

To give you an example: I worked on a project where all the “technical” and business required goals were met, even far exceeded an accepted minimum level of quality measures, but the project itself failed because the final customer was no longer interested in the service.

With DevOps we now bring value quicker to the end user so these type of failures will not cause a huge investment of money and time. But I still haven’t found criteria to use in validating the quality of a project on a subjective level. Anyone who has experience with this and cares to share?

1 Like

I don’t really believe that “devops” is critical in making a customer happy or unhappy. I also don’t believe that “marketplace testing” falls into the remit or the pay grade of a SDET. The finance+marketing+sales departments, one assumes have some kind of testing mindset, it’s not an engineering function. I regularly remind external teams that it’s not down to my team at all. The only thing we control is timescale and cost. And cost (time and money) is the thing we bring up, especially if it means big cloud subscriptions. I once attended a very good talk at a meetup from someone who was flaying themselves over failing to check that the product was actually going to be saleable, within the whole “risk testing” argument.

It is weird talking someone into stopping believing that they are at fault due to an external factor.


DevOps can definitely bring value faster to clients , but it will depend on the type of issue the user is experiencing, right?
Database teams can also provide value in a similar way. For Dev teams that would not be the case.

Aaaaaand if you think of it, even support can help customers get more value out of a system . For example: a feature breaks and there is a workaround the user doesn’t know but support lets them know how to use it until the fix is in live. That also generates value and the customer is not as mad as he could be , he in fact can be happy because of the service provided. Thoughts?

1 Like

We often forget that quality is also about how we respond and plan for our failures in order to move forward more freely with lower entanglement. Cool spot Lleana.

1 Like