> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide.md).

# Over Time Quality Improvement Guide

**Software quality isn't a sprint; it's a marathon.** Over Time Quality Improvement recognizes this, offering a strategic, long-term approach that transcends individual releases. By setting a clear vision and making incremental progress, you can cultivate enduring quality in your software.

**What sets Over Time Quality Improvement apart?**

* **Focus on the big picture:** Goes beyond individual releases, aiming for sustained improvement across the entire software lifecycle.
* **Incremental progress, lasting impact:** Instead of chasing quick fixes, it prioritizes systematic, step-by-step improvements for long-term benefits.
* **Test gaps are your roadmap:** Over Time Quality Improvement actively identifies and addresses test gaps, paving the way for comprehensive coverage and increased confidence.

***

### Implementation

Incorporate these steps into your processes with SeaLights:

{% content-ref url="/pages/MBxwu0kmF3hneP95BGTP" %}
[STEP 1: Deploy SeaLights](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-1-deploy-sealights.md)
{% endcontent-ref %}

{% content-ref url="/pages/ikUcJuXNItAs9bOtaJL5" %}
[STEP 2: Take a Quality Snapshot](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-2-take-a-quality-snapshot.md)
{% endcontent-ref %}

{% content-ref url="/pages/RfRNT8Du0EpJgIPCPAZo" %}
[STEP 3: Prioritize Code Areas](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/release-quality-improvement-guide/step-3-prioritize-code-areas.md)
{% endcontent-ref %}

{% content-ref url="/pages/10iW3293JjMoPMWPe56Y" %}
[STEP 4: Set Baseline & Goal](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-4-set-baseline-and-goal.md)
{% endcontent-ref %}

{% content-ref url="/pages/WymD99CCULAnn9lkB5ox" %}
[STEP 5: Set timeline](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-5-set-timeline.md)
{% endcontent-ref %}

{% content-ref url="/pages/oATPjAA1EpxDiswvh1vq" %}
[STEP 6: Write tests](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-6-write-tests.md)
{% endcontent-ref %}

{% content-ref url="/pages/6f1hm6AUoyjVrtTX75OK" %}
[STEP 7: Monitor progress](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-7-monitor-progress.md)
{% endcontent-ref %}

{% content-ref url="/pages/zYwUPJkrYTgEFurGllxi" %}
[STEP 8: Measure Defect Escape Rate](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-8-measure-defect-escape-rate.md)
{% endcontent-ref %}

By embracing Over Time Quality Improvement, you can unlock the power of continuous improvement and build software that stands the test of time. Remember, quality isn't built overnight; it's a journey of dedication and commitment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.