> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/user-story-coverage/use-cases-by-persona/managers/informed-go-no-go-decisions-making.md).

# 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](/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/ZhUDviik0KXJhAQYsSi2)
* Adjust the scope if needed using the [How to Generate / Edit the Report](/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/WqnX33aQ1MeGNeZOiiJK" 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 %}