> For the complete documentation index, see [llms.txt](https://help.usehaystack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usehaystack.io/setup/teams/sprint-success-metric.md).

# Sprint success metric

Setup a key metric for your team that helps you evaluate the success of a sprint.

### Basics

Haystack provides two options as a sprint success metric:

1. **Completion Rate** (default): the percentage of work completed against the total sprint scope, including any scope changes during the sprint.
2. **Commitment Reliability**: the percentage of work completed from the initial sprint plan, excluding any scope changes mid-sprint. Choose this metric if you want to: 
   1. Ensure team stays on track with original sprint commitments
   2. Identify gaps between planned and completed work

### What will be impacted

Based on your sprint success metric selected in settings, you will see changes in all sprint-related pages: Issues, Retro, Sprint review.

{% tabs %}
{% tab title=" Issues" %}

<figure><img src="/files/ZFNYZwgxk30pBxTz9wCq" alt=""><figcaption><p>Sprint success metric is shown in overview section</p></figcaption></figure>
{% endtab %}

{% tab title="Retros" %}

<figure><img src="/files/2kiK74dh6hHwllwwnYZk" alt=""><figcaption><p>Sprint success metric is shown in retros page table</p></figcaption></figure>

{% endtab %}

{% tab title="Sprint review" %}

<figure><img src="/files/USZph9uOvli8xd1sQXcu" alt=""><figcaption><p>Sprint success metric is shown in retros page table</p></figcaption></figure>
{% endtab %}
{% endtabs %}

### Setup

1. Head to the [Teams Settings](https://dash.usehaystack.io/hub/settings) page via the Settings icon on the left sidebar

   <figure><img src="/files/IpWJJvizO75TEySDv5Lv" alt=""><figcaption></figcaption></figure>
2. Navigate to '[Board](https://dash.usehaystack.io/hub/settings/board)' settings and select metric in "Sprint success metric" section:

   <figure><img src="/files/yN7hLOIR2FUavS33UYFo" alt=""><figcaption></figcaption></figure>
3. Click Save.

## FAQ <a href="#h_2f967536f7" id="h_2f967536f7"></a>

<details>

<summary>Does the 'Sprint Success Metric' apply retroactively?</summary>

Yes, metric will be applied retroactively to all past sprints for the team.&#x20;

</details>

<details>

<summary>Do issues removed mid-sprint impact commitment reliability?</summary>

Yes, removing issues mid-sprint is considered a scope change and will affect the sprint reliability metric.

</details>

<details>

<summary>Does a high Commitment Reliability indicate a successful sprint?</summary>

Not necessarily. While high Commitment Reliability indicates good planning, factors like long-term goals, value delivered, and team capacity are equally important.

</details>

<details>

<summary><strong>When should Commitment Reliability be used over Completion Rate?</strong></summary>

Commitment Reliability is ideal for improving sprint planning accuracy, assessing adherence to initial commitments, reducing scope changes, and enhancing delivery predictability.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.usehaystack.io/setup/teams/sprint-success-metric.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.