# Work Progress

Work progress represents the percentage breakdown of Issue tickets or Story points in the selected sprint according to their current workflow status.

Typo considers all the issues in the sprint and categorizes them based on their current status category, using your JIRA status category mapping. It shows three major categories by default: Open, In Progress, and Done. These can be configured as per your custom processes.\
In the case of a closed sprint, Typo only shows the breakup of work on a ‘Completed’ & ‘Not Completed’ basis. If a task is ‘Not Completed’ in the selected sprint but is ‘Completed’ in the future sprint, it will still be shown as ‘Not Completed’.

<div align="left"><figure><img src="/files/wvy1x7zT564YsC9FcWmM" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/WtZGse3ckTMs3Klx2k07" alt=""><figcaption></figcaption></figure></div>

### **How does tracking work breakup help in sprint analysis?**

Tracking work progress provides valuable insights into engineering teams' work status and efficiency during a sprint. Here are a few points highlighting how monitoring work progress contributes to improving the efficiency of engineering teams:

1. **Visibility and Transparency:** By tracking work progress, teams gain visibility into the status of individual tasks or stories within the sprint. This promotes transparency across the team, allowing members to understand what work is in progress, completed, or blocked, facilitating better collaboration and coordination.
2. **Identifying Bottlenecks:** Work progress metrics help identify bottlenecks or blockers in the workflow. Teams can quickly identify tasks that are stalled or facing delays, allowing them to address issues and keep the work flowing smoothly and proactively. This prevents work from piling up and ensures the team stays on track to meet sprint goals.
3. **Optimizing Workflows:** Insights from work progress data enable teams to optimize their workflows and processes. By analyzing the distribution of tasks across different workflow statuses, teams can identify areas where work tends to get stuck or delayed. This allows them to streamline workflows, eliminate unnecessary handoffs, and implement process improvements to accelerate work progress.


---

# 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://typo.gitbook.io/typo-help-docs/engineering-metrics/sprint-metrics/work-progress.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.