Continuous Quality

Continuous Quality is building quality in at every stage possible — Stuart Day

Continuous quality (CQ) is an engineering practice that measures, monitors, improves, and debugs software quality throughout the software development life cycle (SDLC). This practice aims to evaluate the quality of the software with every code change made in the system. CQ is an important component of continuous integration (CI) and continuous delivery (CD). CQ is typically implemented before CD. This is because CQ helps to ensure that the software is of high quality before it is deployed to production. As an industry, we have embraced continuous deployment. This means that software is continuously deployed to production, often multiple times a day. The need to implement CQ is imperative in order to ensure that the software is of high quality and that it meets the needs of users. — Rakesh Sukla

To me, it’s more or less about baking in quality from the start, always having an eye on the state of an SUT and how to improve it as you go along. This would be in contrast to building a thing entirely before thinking about whether or not it actually solves a problem or adds any value or whether anyone would actually want to use it. - Cassandra H. Leung

In my opinion, in agile, when the product is deployed continuously through the CI/CD pipeline, it is important to maintain quality, and that too continuously. Hence, continuous quality is a journey of maintaining quality while the team introduces or modifies features, fixes bugs, refactors code, etc. in every sprint. — Ujjwal Kumar Singh

There are bound to be many different definitions of Continuous Quality, just as there are with many things related to the term Quality.

Personally, I believe it refers to something bigger than just the SDLC. There are so many elements that need to come together in order to achieve Quality and not all of them are obviously a part of the SDLC in it's simplicity of Ideation to Production. — Philippa Jennings