Threats to Quality

Threats to Quality

If, as Gerry Weinberg states Quality is “value to some person” …then the corollary stands that risk is anything that threatens that value.

This can be useful because Quality is an amorphous, shapeshifter, notoriously difficult to nail down. Its final judge is not us but our consumers.

I compare quality to a Black Hole. We can’t see it, we infer it exists through observing the impact on nearby matter. In the same vein, we don’t see quality, but we know it exists by how our consumers respond to it.

Unlike black holes, we can influence product quality. We do this my focus on what prevents us from producing quality work. By identifying and removing anything that threatens to impact our ability to design, develop and deploy a quality product.

One way to identify threats to quality is to ask yourself: “what is preventing me from getting meaningful work done?” The answer is likely to be a threat to quality.  Frustrated by flaky tests? Poorly maintained test environments?  No version control?

In the context of emergent quality, threats would be any practices, processes, technologies, and yes people, that prevent you from achieving the business goals, nested bets and outcomes set out by your team, CTO and/or company.

Threats to quality are understandably seen as undesirable and often shoved under the carpet to get ‘real work’ done. Consider identifying and removing threats is part of the real work. It’s how we handle product quality when we no longer have full control of the product.

We will always have threats to quality.  How we make them visible and how we deal with them in a consistent and measured way may be the future of how we measure quality.

Emergent Quality
If you work in software development, like I do, you most likely work within a complex system. You also, most likely, work on a complex system. Not sure? Try answering these questions: Is it hard to model your system in all its complexity?Is it hard to work
Contemporary Quality Engineering
Some randomish thoughts on quality engineering.  Quality engineering enables visualisation of the state of quality anytime in the delivery lifecycle of a system or service. It does so in terms of its business outcome.  Anne-Marie Charrett  (working definition) Services not Products&…
Quality is a journey - but do you know your destination?
After any decent exposure to software testing, Jerry Weinberg’s definition of quality tends to gain traction and respect. That is “Quality is value to some person”. You like it because of its subjectivity. You may also hate it because of its subjectivity. Remember that bug repor…
When the rubber hits the road
Anyone who has attempted to create and then implement a strategy, will know there’s a big difference between what is intended when the strategy is written, and what is realised on implementing a strategy. To the point in software testing, there’s been a push away from

Comments

Sign in or become a Anne-Marie Charrett (aka Maverick Tester) member to read and leave comments.