Engineering Quality Principles

Introduction

These Quality Principles govern the Software Development Life Cycle (SDLC) and serve as the framework for engineering standards, process alignment, and automated or manual quality assessments. They define a baseline that teams, pipelines, and review agents SHOULD evaluate work against; deviations SHOULD be justified and documented.

Core Principles

1. Quality is Integrated into Each Step of the SDLC

Statement: Quality MUST be embedded into every phase of the SDLC and form an explicit part of the Definition of Done; it is not a separate phase that happens after development, nor the responsibility of a single role.

2. Quality is More Than Testing

Statement: Testing is a subset of quality. Quality engineering also drives continuous improvement and the identification, prioritisation, and mitigation of system bottlenecks across the entire lifecycle.

3. Quality is a Team Responsibility

Statement: Quality is a collective ownership. Every role in the SDLC — Development Managers, Architects, Business Analysts, Software Engineers, and Quality Engineers — is actively responsible for achieving and maintaining quality standards.

4. Smart Automation

Statement: Any repetitive testing task that is feasible to automate SHOULD be automated, implemented at the most efficient layer of the testing pyramid, and MUST NOT duplicate checks already covered by a lower layer.

5. Reduce Waste

Statement: Every quality activity MUST deliver value justified by its return on investment. Activities that cannot be justified — automated tests, suites, process steps, or manual stages — SHOULD be removed.

6. Release as Often as Possible

Statement: Production releases SHOULD happen frequently as small, incremental updates on a healthy, production-ready pipeline. Unfinished features SHOULD be deployed safely behind feature flags rather than held back on long-lived branches.

7. Shift Left

Statement: Quality activities MUST begin at the inception of a feature. The primary objective is to prevent defects rather than find them, even when this requires adjusting development priorities to build testable features.

8. Shift Right

Statement: Quality assurance does not end at release. Monitoring live systems, analysing real-world behaviour, and proactively keeping production environments healthy and stable are an integral part of quality scope.

Applying These Principles