> 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/challenges-and-approach-comparison/choosing-the-right-approach.md).

# Choosing the Right Approach

Explore the specific processes, tools, and practices involved in each approach to gain valuable insights. 

{% embed url="<https://youtu.be/2Nklfb9ejgM>" %}

After understanding both approaches, review the following summary to ensure you choose the one that best fits your needs.

<table data-full-width="true"><thead><tr><th width="272.3333333333333">Comparison</th><th>Release Process</th><th>Over Time Process</th></tr></thead><tbody><tr><td><strong>Organization Culture</strong></td><td><mark style="color:purple;"><strong>Enforcement -</strong></mark><br>Embedding processes, fostering an environment where individuals are committed to following guidelines and regulations. It focuses on compliance, accountability, and ensuring consistency.</td><td><mark style="color:purple;"><strong>Empowerment -</strong></mark><br>Promoting autonomy, trust, and collaboration, empowering individuals to make decisions and take ownership. It encourages self-reliance, innovation, and a sense of responsibility, free from rigid rules and hierarchy.</td></tr><tr><td><strong>Dev/QA Collaboration</strong></td><td>Dev and QA have <mark style="color:purple;"><strong>easy access</strong></mark> to each other, or have regular meetings once every few days.</td><td>Collaboration between Dev and QA is <mark style="color:purple;"><strong>very limited</strong></mark>.</td></tr><tr><td><strong>Velocity of Writing Tests</strong></td><td>There are sufficient resources available to write and execute critical tests within a release.</td><td>There are insufficient resources to address test gaps within a release.</td></tr><tr><td><strong>Maturity</strong></td><td><p>Implemented <mark style="color:purple;"><strong>at least one</strong></mark> of the following practices:</p><ul><li>Shift-left testing</li><li>Agile / SAFe teams</li><li>Microservices</li><li>Test automation</li></ul><p>other processes in the SDLC are in place and operating smoothly.</p></td><td><p></p><p><mark style="color:purple;"><strong>None</strong></mark> of the following practices are currently in place or are still at the early planning stages:</p><ul><li>Shift-left testing</li><li>Agile / SAFe teams</li><li>Microservices</li><li>Test automation</li></ul></td></tr><tr><td><strong>Product Impact</strong></td><td><mark style="color:purple;"><strong>High</strong></mark> impact of the product / feature on the overall success and functionality of the business.</td><td><mark style="color:purple;"><strong>Low or medium</strong></mark> impact of the product / feature on the overall success and functionality of the business.</td></tr></tbody></table>

If the descriptions of the Release process resonate more with your organization, it is advisable to start with this implementation. However, if your organization aligns better with the descriptions of the Over Time process, it may be more practical to stick with that approach rather than starting with the Release process. The over time approach can be easier to implement as it doesn't require changes to your development lifecycle.

### **Which approach best fits for your organization?**

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;">Release Quality Improvement</mark></td><td></td><td></td><td><a href="/pages/u1zyOwzEDIWt9OSpoNEW">/pages/u1zyOwzEDIWt9OSpoNEW</a></td></tr><tr><td><mark style="color:blue;">Over Time Quality Improvement</mark></td><td></td><td></td><td><a href="/pages/WoGdO0zs7q9J4oqJElh9">/pages/WoGdO0zs7q9J4oqJElh9</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/guides/quality-improvement/challenges-and-approach-comparison/choosing-the-right-approach.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.