> 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/overall-progress-monitoring.md).

# Overall Progress Monitoring

As a manager, the User Story Coverage Report is your secret weapon for quality control. Gain real-time insights, make data-driven decisions, and ensure high-quality software through proactive monitoring and early intervention.

***

## Step-by-Step Tutorial

<details>

<summary><strong>1. Access the Report</strong></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><strong>2. 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><strong>3. Monitor Coverage Throughout the Development Cycle</strong></summary>

* Track user stories and subtasks progressing through code review, testing phases, and approval.
* Analyze both Modified Coverage and Non-Unit Tests Coverage for each story, providing a holistic view of testing progress.

</details>

<details>

<summary><strong>4. Early Identification of Gaps</strong></summary>

* Be alerted to stories or subtasks with 0% or very low coverage, prompting immediate collaboration with development and QA teams.
* Proactively address situations where specific test types show low coverage, ensuring tests are planned or resources allocated.

</details>

<details>

<summary>5. <strong>Establish a Culture of Continuous Monitoring</strong></summary>

* Conduct regular meetings (weekly or bi-weekly) with QA and development teams to jointly monitor quality progress.
* Make informed decisions throughout the development cycle, avoiding surprises at the end of sprints or release cycles.

</details>

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