> 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/step-5-set-timeline.md).

# STEP 5: Set timeline

{% hint style="info" %}
Typically, this step is done by QA Manager/Architect or Engineering Manager.
{% endhint %}

Setting a **4-6 month timeline** for your quality improvement journey ensures you have the **time and space for meaningful progress**. Think of it as a marathon, not a sprint, where steady steps lead to lasting impact.

### **Checkpoint Power-Ups**

* **Embed regular milestones:** Break down your journey with **predefined checkpoints at consistent intervals**.
* **Monitor and adjust:** Use these checkpoints to **gauge your progress** and **make adjustments** if needed.
* **Informed decisions:** Regularly reviewing your progress empowers you to **make data-driven adjustments** to your strategies and testing approach.

***

### **Tips**

* **Milestones fuel motivation:** Celebrate progress at each checkpoint to keep your team engaged and energized.
* **Flexibility matters:** The timeline is a guide, not a rigid rule. Adapt it based on your progress and learnings.
* **Continuous improvement is key:** Embrace the checkpoints as opportunities to refine and optimize your quality journey.


---

# 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/step-5-set-timeline.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.