Blog Retrospective #2

I completed the next twenty posts, bringing the total to forty. Since I agreed with myself to pause for a retrospective after every twenty posts, here is the second one. It feels as though I have completed an initial theoretical loop around product quality assessment.

During this cycle, the investigation moved through several connected questions:

• What distinguishes assessment from testing, QA and quality engineering?
• What must exist before meaningful assessment is possible?
• What belongs in a product reference model?
• Who owns and maintains that model?
• How should evidence support judgement?
• How does assessment continue after deployment?

The final field notes brought many of these questions together in Product Quality Assessment as a Continuous Discipline.

What Surprised Me?

The biggest surprise was the growing importance of the product reference model. It began as the reference against which a product could be assessed. It gradually became something closer to a shared description of what the product is intended to achieve, what good looks like, which constraints matter and what evidence is needed.

A second surprise was the emergence of Product Ownership as the continuity mechanism connecting business intent, engineering interpretation, release judgement and operational learning.

A third surprise was that the field notes began reinforcing one another. Ideas that appeared speculative in isolation became more credible when placed into a coherent chain.

What Became Clearer?

Several propositions now seem reasonably stable:

• Quality is the integrity of the chain from business intent to realised outcome.
• Testing can be understood as a form of assessment, but product quality assessment is broader than testing.
• Meaningful assessment requires an explicit reference model.
• The reference model must guide implementation as well as evaluation.
• Assessability and evidence need to be designed in.
• Product quality cannot be fully understood at release. Operational evidence must complete the judgement.

These are still working propositions, but they increasingly appear to form a coherent whole.

What Remains Unproven?

The theory has not yet been validated as an operational model. Important questions remain:

• Can a useful product reference model be maintained without becoming bureaucratic?
• What is its minimum viable form?
• Can product quality assessment become part of normal delivery rather than a separate governance process?
• Does it lead to better findings, decisions and priorities in practice?

The business-intent side also needs more development. Much of the thinking so far has focused on engineering, testing, evidence and reference models.

What Comes Next?

The next step is probably not another rapid expansion of the theory. I want to begin consolidating the existing thinking around one master theme:

Quality from Business Intent to Outcome

Supporting themes may include:

1. Testing as Assessment
2. The Product Reference Model
3. Product Ownership and Quality Judgement
4. Continuous Product Quality Assessment

These should be treated as evolving synthesis pages rather than finished statements.

For the field notes, I first want to propose a conceptual table of contents for the product reference model. After that, I expect to return to assessment itself: the assessment model, the relationship between evidence and judgement, and perhaps a few conceptual capability models.

I also want to revisit a historical assessment and see whether the emerging approach produces better or simply different findings.

Conclusion

The first retrospective asked what was happening to the writing process. This retrospective asks what has happened to the subject itself.

Product quality assessment began as an attempt to describe testing differently. It expanded into questions about reference models, Product Ownership, evidence, operational learning and governance.

The result is not yet a proven method. But it is becoming a coherent discipline. The next step is to find out whether it can also become concrete, usable and valuable in practice.