# Issues At-Risk

Issues At-Risk highlights those Issue tickets in the ongoing sprint that are at a potential risk of not getting completed on time. This acts as a proactive measure to keep track of such Issues to ensure timely delivery of sprint.

Typo runs a predictive algorithm to highlight such Issues in the sprint that have a risk of delayed delivery. There are multiple factors taken into consideration while flagging such issues:

* If the issue has been ‘In Progress’ state for 2 or more days with no activity
* If the issue is still ‘In Progress’ state & the sprint closure is in the next 72 hours or more
* If there hasn’t been any activity on an issue for long\
  & more.

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2FE6UyHgVz5vydeaAhOZFY%2FScreenshot%202025-06-26%20173805.png?alt=media&#x26;token=47b12aaf-0da1-49ee-966a-5a729e867ac4" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2FT3yfgrgTHHDl17EEnbOd%2FScreenshot%202025-06-26%20133239.png?alt=media&#x26;token=8fb4c787-6cce-4be5-9eb0-4495cf1804e2" alt=""><figcaption></figcaption></figure></div>

### **How does tracking issue at-risk help in sprint analysis?**

Tracking issues labeled as "at-risk" is essential for sprint analysis as it helps teams anticipate and address potential challenges, maintain progress toward sprint goals, and drive continuous improvement in agile software development projects.

1. Early Risk Identification: Tracking issues labeled as "at-risk" helps in identifying potential blockers or challenges early in the sprint. By flagging issues that are at risk of not being completed on time, teams can proactively address them before they escalate into larger problems.
2. Resource Allocation: Monitoring at-risk issues allows teams to allocate resources more effectively. By identifying tasks that are in danger of falling behind schedule, teams can reallocate resources or prioritize work to ensure that critical tasks are completed on time.
3. Sprint Progress Monitoring: Tracking at-risk issues provides visibility into the overall progress of the sprint. Teams can monitor the number of at-risk issues over time and assess whether the sprint is on track to meet its goals. This helps in making informed decisions about adjusting priorities or timelines as needed.
4. Mitigating Risks: Identifying at-risk issues enables teams to take proactive measures to mitigate risks and prevent delays. Teams can collaborate to resolve blockers, re-evaluate priorities, or seek additional support to ensure that at-risk tasks are completed on schedule.
5. Stakeholder Communication: Monitoring at-risk issues facilitates transparent communication with stakeholders. Teams can provide timely updates on the status of at-risk tasks, discuss potential impacts on project timelines, and work together to address any concerns or challenges.
6. Continuous Improvement: Tracking at-risk issues provides valuable data for retrospective analysis. Teams can review the root causes of at-risk issues, identify patterns or trends, and implement process improvements to prevent similar issues from occurring in future sprints.


---

# 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/issues-at-risk.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.