> 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/effective-resources-prioritization.md).

# Effective Resources Prioritization

The User Story Coverage Report empowers managers to allocate resources effectively and achieve high-quality releases. Learn how to harness the report for data-driven resource prioritization.

***

## Step-by-Step Tutorial

<details>

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

* Navigate to your relevant Jira project and locate the User Story Coverage report within the Sheets page.
* 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 for creation.

</details>

<details>

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

* Verify the report covers the intended timeframe using the Scope icon at the bottom right. ![](/files/ZhUDviik0KXJhAQYsSi2)
* Adjust the scope as needed, referring to 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><strong>3. Analyze Coverage</strong></summary>

* **Simplify View:** Collapse subtasks under user stories (or your hierarchy) for better visualization.\ <img src="/files/o0KN34RXyfzNu9UO2IPg" alt="" data-size="original">
* **Review Metrics:** Analyze both Modified Coverage and Non-Unit Tests Coverage for each user story.

</details>

<details>

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

* **Focus on Low Coverage:** Expand user stories below 100% to pinpoint specific subtasks lacking tests.
* **Verify Satisfactory Subtasks:** For sufficiently covered subtasks, ensure alignment with your testing strategy (e.g., API testing for relevant changes).
* **Address Specific Test Types:** For stories with 100% overall coverage, assess individual test type coverage against your standards. Identify responsible subtasks for any deficiencies.

</details>

<details>

<summary><strong>5. Craft a Testing Plan</strong></summary>

* **Categorize Gaps:** Create separate lists for:
  * Uncovered subtasks.
  * Subtasks with low coverage.
  * Subtasks lacking crucial test types (based on your strategy).
* **Assign Ownership:** Match each list item with its parent user story for context.

</details>

<details>

<summary><strong>6. Prioritize Resources</strong></summary>

**Strategic Allocation:** Follow this sequence:

* Address uncovered subtasks first, as they represent complete testing absence.
* Move to subtasks with low coverage, prioritizing based on severity and impact.
* Assign relevant individuals to cover subtasks within critical test types, focusing on sensitive code sections and those containing critical functionality.

</details>

{% hint style="info" %}
**Remember:** This framework serves as a foundation. Adapt it to your specific organizational needs, testing strategies, and resource availability.
{% endhint %}