# Carry over

Refers to issues/story points that were not completed in the sprint & moved to later sprints

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2F5DvxkkPloPtvhbfu3ZKo%2FScreenshot%202025-06-26%20132903.png?alt=media&#x26;token=d0ad7f18-7447-41c8-ac73-6be3de569d4e" alt=""><figcaption></figcaption></figure></div>

### **How does tracking carry-over help in sprint analysis?**

Tracking carry-over items in sprint analysis enables teams to optimize planning, execution, and delivery processes, resulting in improved productivity, predictability, and project outcomes.

1. **Performance Evaluation:** Monitoring carry-over items allows teams to assess their sprint planning accuracy and execution efficiency. By identifying the number and type of issues that were not completed within the sprint, teams can evaluate their performance against initial sprint commitments.
2. **Root Cause Analysis:** Analyzing carry-over items helps teams uncover underlying reasons for incomplete work. Whether due to underestimated effort, dependencies, technical challenges, or other factors, identifying the root causes enables teams to address them effectively and improve future sprint planning and execution.
3. **Workload Management:** Tracking carry-over items assists teams in managing workload and capacity planning for subsequent sprints. By understanding the volume and nature of unresolved work, teams can allocate resources more effectively, adjust sprint goals, and prioritize tasks to ensure successful sprint completion.
4. **Risk Identification:** Carry-over items highlight potential risks and challenges that may impact future sprint deliverables and project timelines. Teams can proactively address these risks by allocating additional resources, revising sprint goals, or implementing mitigation strategies to minimize their impact on overall project success.


---

# 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/carry-over.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.