# Informed Go/No Go Decisions Making

As a manager, the User Story Coverage Report serves as a valuable tool for evaluating the quality of software development efforts and making informed decisions regarding code changes. This informed approach helps you make sound go/no-go decisions and confidently present your team's work to the change advisory board.

***

## Step-by-Step Tutorial

<details>

<summary>1. Access the Report</summary>

* Navigate to your relevant Jira project and open the Sheets page with the User Story Coverage report.
* If unavailable, follow the [How to Generate / Edit the Report](/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report/how-to-generate-edit-the-report.md) guide to create it.

</details>

<details>

<summary>2. <strong>Ensure Scope Accuracy</strong></summary>

* Verify the report covers the desired timeframe by checking the Scope icon at the bottom right.\
  ![](/files/lDyvnNPA3lFiuHLqTCM9)&#x20;
* Adjust the scope if needed using the [How to Generate / Edit the Report](/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report/how-to-generate-edit-the-report.md) guide.

</details>

<details>

<summary>3. Analyze Coverage</summary>

* **Collapse subtasks:** Simplify viewing by collapsing subtasks under user stories (or your hierarchical structure).\ <img src="/files/Myv6OoaS9l4lNPKlxJsA" alt="" data-size="original">
* **Review coverage:** Analyze both Modified Coverage and Non-Unit Tests Coverage for each user story.

</details>

<details>

<summary>4. <strong>Identify Gaps</strong></summary>

* **Focus on low coverage:** Expand user stories with less than 100% coverage to pinpoint specific subtasks lacking tests.
* **Verify satisfactory subtasks:** For subtasks with sufficient coverage, ensure they align with your testing strategy (e.g., API changes needing API testing).
* **Address specific test types:** For user stories with 100% overall coverage, check individual test type coverage against your organization's standards. If any fall short, identify the responsible subtasks.

</details>

<details>

<summary>5. <strong>Action Plan</strong></summary>

* **Create testing plan:** Address uncovered areas by outlining clear testing steps before production deployment.
* **Approve readiness:** Sign off on user stories (or features) if all testing is complete and satisfactory.

</details>

<details>

<summary>6. <strong>Change Advisory Board (CAB) Presentation</strong></summary>

* If your organization requires CAB approval before release, present the report during the meeting.
* **Export option:** Alternatively, export the report for inclusion in other presentation materials.

</details>

{% hint style="info" %}
**Remember:** This guide provides a general framework. Adjust it to your specific organizational needs and testing strategies.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.sealights.io/knowledgebase/guides/user-story-coverage/use-cases-by-persona/managers/informed-go-no-go-decisions-making.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.