Product quality is often assessed at particular moments:
- A requirement is reviewed.
- A feature is tested.
- A release decision is made.
- An incident is investigated.
- Customer feedback is analyzed.
Each activity may produce useful evidence. But when they remain disconnected, no one continuously maintains the overall basis for judging the product. If quality is the integrity of the chain from business intent to business outcome, product quality assessment cannot be reduced to a single test phase or release gate. It must become a continuous discipline.
Assessment Begins With Intent
Before a product can be assessed, there must be a basis for judgment. What is the product intended to achieve? For whom? Under which conditions? Which qualities matter? Which constraints must be respected? What evidence would indicate success or failure? Together, these expectations form the product reference model.
Requirements and acceptance criteria may be part of that model, but they are not the whole of it. The model may also include intended outcomes, stakeholder needs, quality characteristics, risks, assumptions, operating conditions and evidence requirements.
Without such a model, testing may still find defects. But it becomes much harder to judge whether the product as a whole is fit for its intended purpose.
The Model Must Feed Development
The reference model should not be created only so that someone can assess the finished product. It must also guide the people building it. Quality expectations have design implications. Performance expectations influence architecture. Auditability requires traceability. Resilience requires detection and recovery mechanisms. Business outcomes require ways to observe whether those outcomes occurred.
The question is therefore not only whether an expectation can be tested later. It is whether the product is being designed to satisfy the expectation and produce the evidence needed to assess it. Assessment begins before implementation because the basis for later judgment influences what must be built.
Evidence Accumulates Across the Lifecycle
Testing provides essential evidence, but it provides only part of the picture. Reviews, analysis, demonstrations, security checks and performance tests may contribute evidence before release. Monitoring, incidents, support cases, user behavior and business results contribute evidence after release. Some qualities can be assessed with confidence before deployment. Others can only be fully understood in operation.
Continuous product quality assessment brings these sources together rather than treating them as separate activities belonging to different functions. The purpose is not to gather as much evidence as possible. It is to gather the evidence needed to make responsible judgments about the product.
Judgment Must Be Explicit
Evidence does not make decisions by itself. Someone must interpret what the evidence means in relation to the reference model, the remaining uncertainty and the risks involved. Is the product ready to release? Are known limitations acceptable? Did the product create the intended outcome? Has new operational evidence changed what the organization believes about it?
Product Ownership safeguards the coherence of the product reference model. Specialists contribute evidence and professional judgment. Leadership sets strategic direction, constraints and acceptable risk. Assessment integrates these perspectives into a product-quality judgment.
The Cycle Does Not End at Release
A release is not the conclusion of product quality assessment. It is the point at which new forms of evidence become available.
Real use may reveal that assumptions were wrong. Customers may value different outcomes than expected. Operational conditions may expose risks that pre-release testing could not reproduce. A product may function correctly and still fail to produce the intended business result.
This evidence should not only lead to fixes. It should update the product reference model itself. The continuous cycle becomes:
intent → reference model → development → evidence → judgment → operation → learning → revised intent
The product changes. Its context changes. What the organization knows about it changes. The basis for judging it must change as well.
A Discipline, Not an Additional Phase
Product quality assessment is not a new phase wrapped around testing. It is the continuous discipline of maintaining the basis for product-quality judgment from intent to outcome. Testing remains essential. QA and quality engineering remain valuable. Product Ownership, operations and leadership all retain their distinct responsibilities. But their contributions become more useful when they support one coherent and continuously updated judgment of the product.
Quality is not established once. It is assessed, learned from and reassessed throughout the life of the product.
Leave a Reply