# Retrospective

This blog will go over how to use [Retros](https://delivery.usehaystack.io/team/retrospective) page in Haystack.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016349438/ca85aa0712e35bba5a736a4a/Screen+Shot+2024-04-09+at+4_49_52+PM.png" alt=""><figcaption></figcaption></figure>

## Multiple Sprints / Weeks <a href="#h_3a442a572a" id="h_3a442a572a"></a>

*Note: Retrospective page has different views for Kanban & Sprints boards. The Kanban version will be a trimmed down version of the Sprint one.*

### Completion Rate <a href="#h_644d874c5f" id="h_644d874c5f"></a>

{% hint style="info" %}
Only available in Sprint teams.
{% endhint %}

Completion Rate metric changes based on[ Issues vs Points setting](#h_cd813559c8).

* **Issues Calculation**: `Issues Completed in Sprint / Total Issues in Sprint`
  * **Issues Completed in Sprint**: In the end of a sprint, any issue that is still part of sprint and has Status Category as `Done`
  * **Total Issues in Sprint**: In the end of a sprint, any issue that is still part of sprint.
* **Points Calculation**: `Story Points Completed in Sprint / Total Story Points in Sprint`
  * **Points Completed in Sprint**: In the end of a sprint, any issue that is still part of sprint and has Status Category as `Done` .
  * **Total Points in Sprint**: In the end of a sprint, any issue that is still part of sprint.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016350248/f91af49acb750bd426008650/Screen+Shot+2024-04-09+at+4_50_31+PM.png" alt=""><figcaption></figcaption></figure>

***Note:***

* You can check every issue that was included in the calculation by [drilling inside specific Sprint/Week Reports.](#h_b24df9c819)
* For "Points Calculations" if an issue does not have story points attached to it, it is simply counted as 0.
* Haystack uses Status Category to standardized Completion Rate across different teams
* You can read more about [What is Status Category?](https://help.usehaystack.io/faq/what-is-status-category)

### Issues Completed <a href="#h_4338c3aeae" id="h_4338c3aeae"></a>

{% hint style="info" %}
Available for both Kanban & Sprint teams.
{% endhint %}

Issue Completed metric changes based on [Issues vs Points setting](https://help.usehaystack.io/en/articles/9174347-retrospective#h_970f635696)[.](#h_cd813559c8)

* **Issues Calculation**: `Issues Completed in Sprint/Week`
  * **Issues Completed in Sprint/Week**: In the end of a sprint/week, any issue that is still part of sprint/week and has Status Category as `Done`
* **Points Calculation**: `Story Points Completed in Sprint/Week`
  * **Points Completed in Sprint/Week**: In the end of a sprint/week, any issue that is still part of sprint/week and has Status Category as `Done` .

<figure><img src="https://downloads.intercomcdn.com/i/o/1016386212/a81fa9f9866ff1afac49c936/Screen+Shot+2024-04-09+at+5_17_07+PM.png" alt=""><figcaption></figcaption></figure>

***Note:***

* You can check every issue that was included in the calculation by [drilling inside specific Sprint/Week Reports.](#h_b24df9c819)
* For "Points Calculations" if an issue does not have story points attached to it, it is simply counted as 0.
* Haystack uses Status Category to standardized Completion Rate across different teams
* You can read more about [What is Status Category?](https://help.usehaystack.io/faq/what-is-status-category)
* For Kanban teams it's end of week, for Sprint teams it's end of Sprint

### Scope Change <a href="#h_ea038e84a1" id="h_ea038e84a1"></a>

{% hint style="info" %}
Only available in Sprint teams.
{% endhint %}

Scope Change metric changes based on [Issues vs Points setting](https://help.usehaystack.io/en/articles/9174347-retrospective#h_970f635696)[.](#h_cd813559c8)

* **Issues Calculation**: `# of Issues Start of Sprint - # of Issues End of Sprint`
* **Points Calculation**: `# of Story Points Start of Sprint - # of Story Points End of Sprint`

<figure><img src="https://downloads.intercomcdn.com/i/o/1016373769/306f461389b164e36a25fa25/Screen+Shot+2024-04-09+at+5_07_40+PM.png" alt=""><figcaption></figcaption></figure>

***Note:***

* You can check every issue that was included in the calculation by [drilling inside specific Sprint/Week Reports.](#h_b24df9c819)
* Statuses of an issue does not effect the metric. As long as the issue is in sprint it will be counted.
* For "Points Calculations" if an issue does not have story points attached to it, it is simply counted as 0.

### Investments <a href="#h_e1bf47e112" id="h_e1bf47e112"></a>

{% hint style="info" %}
Available for both Kanban & Sprint teams.
{% endhint %}

Investments metric changes based on [Issues vs Points setting](https://help.usehaystack.io/en/articles/9174347-retrospective#h_970f635696)[.](#h_cd813559c8)

* **Issues Calculation**: `Issues Completed in sprint/week tagged as given investment`
  * **Issues in sprint tagged as given investment**: In the end of a sprint, any issue that is still part of sprint and has Status Category as `Done` & tagged as given Investment
* **Points Calculation**: `Story Points in sprint/week tagged as given investment`
  * **Story Points in sprint tagged as given investment**: In the end of a sprint, any issue that is still part of sprint and has Status Category as `Done` & tagged as given Investment

<figure><img src="https://downloads.intercomcdn.com/i/o/1016388528/81956b2f03faad511c728c2e/Screen+Shot+2024-04-09+at+5_19_11+PM.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Learn how to [setup Investment Categories](#h_54589b839b)
{% endhint %}

*Note:*

* You can check every issue that was included in the calculation by [drilling inside specific Sprint/Week Reports.](#h_b24df9c819)
* For "Points Calculations" if an issue does not have story points attached to it, it is simply ignored.
* Haystack uses Status Category to standardized Completion Rate across different teams
* You can read more about [What is Status Category?](https://help.usehaystack.io/faq/what-is-status-category)
* For Kanban teams it's end of week, for Sprint teams it's end of Sprint

## Single Sprint / Week <a href="#h_b24df9c819" id="h_b24df9c819"></a>

You can click on any week/sprint and drill-in into that specific report.

You can check more about Retros Report

<figure><img src="https://downloads.intercomcdn.com/i/o/1016407653/5bea7e68fff234b7d416e6d2/Screen+Shot+2024-04-09+at+5_34_10+PM.png" alt=""><figcaption></figcaption></figure>

### Sprint Goals <a href="#h_c48aef1151" id="h_c48aef1151"></a>

In Jira you can set [sprint goals](https://cdn.zappy.app/ed295ae6dc30f1b4c39e787b983f5806.png). You can see the goals set in Jira inside Haystack.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016435917/1b2e6573090cae42655d12e2/Screen+Shot+2024-04-09+at+5_56_50+PM.png" alt=""><figcaption></figcaption></figure>

### Completion Rate <a href="#h_2ab3ef177a" id="h_2ab3ef177a"></a>

{% hint style="info" %}
Only available in Sprint teams.
{% endhint %}

Read more on [How is Completion Rate Calculated?](#h_2ab3ef177a)

Clicking on "See details" button will show a [modal](https://cdn.zappy.app/df453f24d8ba413fe84c0128d7dce6c6.png) with every issue that Haystack used to calculated this metric.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016419971/bef126f40044c0c90b6cbd5e/Screen+Shot+2024-04-09+at+5_44_04+PM.png" alt=""><figcaption></figcaption></figure>

### Planned vs. Injected <a href="#h_5970b5143a" id="h_5970b5143a"></a>

{% hint style="info" %}
Only available in Sprint teams.
{% endhint %}

* **Committed Issue**: Any issue that was inside the sprint before the sprint started.
* **Injected Issue**: Any issue that was added to the sprint after the sprint started.

Issue Completed metric changes based on [Issues vs Points setting](https://help.usehaystack.io/features/retrospective)[.](#h_cd813559c8)

* **Issues Calculation**: Issues that are tagged as commited or injected
* **Points Calculation**: Points of Issues that are tagged as commited or injected

Clicking on "See details" button will show a [modal](https://cdn.zappy.app/66cc81368bdb369fa82845ae2fc80b19.png) with every issue that Haystack used to calculated this metric.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016425171/8daa207fde166c6aa3fe5c71/Screen+Shot+2024-04-09+at+5_48_28+PM.png" alt=""><figcaption></figcaption></figure>

**Note:**

* To handle edge cases, after a sprint has started, if any issue has been added to the sprint with-in a 10 minute period, Haystack considered them as "Committed Issues". After this grace period ends, all issues added the to sprint will be counted as "Injected Issue"
* For "Points Calculations" if an issue does not have story points attached to it, it is simply counted as 0.

### Investment Categories <a href="#h_54589b839b" id="h_54589b839b"></a>

{% hint style="info" %}
Available for both Kanban & Sprint teams.
{% endhint %}

Read more on [How is Investments are Calculated?](#h_e1bf47e112)

Clicking on "See details" button will show a [modal](https://cdn.zappy.app/cdd01e9f0400b8dad76b4fb0116cfbe9.png) with every issue that Haystack used to calculated this metric.

{% hint style="info" %}
Learn how to [setup Investment Categories](https://help.usehaystack.io/setup/organization/investments)
{% endhint %}

<figure><img src="https://downloads.intercomcdn.com/i/o/1016435423/a0d0bdf475d2667ea2d8dc57/Screen+Shot+2024-04-09+at+5_56_27+PM.png" alt=""><figcaption></figcaption></figure>

### Epic Progress <a href="#h_78ca46d76f" id="h_78ca46d76f"></a>

{% hint style="info" %}
Available for both Kanban & Sprint teams.
{% endhint %}

The bar for each epic shows

* **Blue**: % of issues completed outside of sprint
* **Green**: % of issues completed during of sprint
* **Gray**: % of issues not completed

Clicking on "See details" button will show a [modal](https://cdn.zappy.app/9341080fabb76ccd5f2e20e93f069212.png) with every issue that Haystack used to calculated this metric.

Read more on [How is Epic Progress is Calculated?](https://help.usehaystack.io/features/epics)

{% hint style="info" %}
See [epics page](https://help.usehaystack.io/features/epics) for a broader view
{% endhint %}

<figure><img src="https://downloads.intercomcdn.com/i/o/1016441210/dffa1c91b1bba27bd973e25f/Screen+Shot+2024-04-09+at+6_01_09+PM.png" alt=""><figcaption></figcaption></figure>

### Release Notes <a href="#h_46db9ae9d6" id="h_46db9ae9d6"></a>

{% hint style="info" %}
Available for both Kanban & Sprint teams.
{% endhint %}

Opens Release notes for that sprint.

{% hint style="info" %}
See [release notes](https://help.usehaystack.io/features/release-notes) for a broader view
{% endhint %}

<figure><img src="https://downloads.intercomcdn.com/i/o/1016446073/fbbf1d9c658f8063f6914626/Screen+Shot+2024-04-09+at+6_05_23+PM.png" alt=""><figcaption></figcaption></figure>

## Customizable Views <a href="#h_2db1f329f1" id="h_2db1f329f1"></a>

### Issues vs. Story Points <a href="#h_cd813559c8" id="h_cd813559c8"></a>

You can change all calculations to

* Issues
* Points

where Points represent `Story Points` field in JIRA.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016402420/1d1c039c7b0bc40381cb0bf8/Screen+Shot+2024-04-09+at+5_30_01+PM.png" alt=""><figcaption></figcaption></figure>

The setting will effect on the following metrics

* [Completion Rate](#h_644d874c5f)
* [Issues Completed](#h_4338c3aeae)
* [Scope Change](#h_ea038e84a1)
* [Investments](#h_e1bf47e112)

## Sharing & Export <a href="#h_c571fda660" id="h_c571fda660"></a>

### Export as CSV <a href="#h_f0b044d053" id="h_f0b044d053"></a>

You can export Retro Report in CSV format using the Export button.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016400453/3803de7c971f718765c9b483/Screen+Shot+2024-04-09+at+5_28_37+PM.png" alt=""><figcaption></figcaption></figure>

### Export as Image <a href="#h_0a8637b00c" id="h_0a8637b00c"></a>

You can export Retro Report Drill-in page in PNG format using the Export button.

<figure><img src="https://downloads.intercomcdn.com/i/o/1016450874/a907671d002470506c5ad3d5/Screen+Shot+2024-04-09+at+6_09_37+PM.png" alt=""><figcaption></figcaption></figure>

### Share via URL <a href="#h_041d785e2a" id="h_041d785e2a"></a>

You can export any page in Haystack, including Retrospective pages just by sharing the URL. The URL will have the team & the week/sprint information allowing you to easily share with other teammates.\
​\
​Example: `https://delivery.usehaystack.io/team/{teamId}/review/{reportId}`

***

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

<details>

<summary> Why is first row in Retros page tagged as active?</summary>

&#x20;The [first row](https://cdn.zappy.app/c87ef95a8922bdea013234d7cd35d2a5.png) in Retros page is the only week/sprint that is not completed, thus any number you see there can change during the week.

* Sprint teams, once you complete the sprint
* Kanban teams, once it's Monday

The report will stop being as active and the tag will be removed. Any number you see will freeze unless you change [configurations that effects the page](#h_d7a2e62e6a).

</details>

<details>

<summary>Can Retrospective page numbers change?</summary>

Except for the [first row](#h_4590049b74), all numbers are static.

Once the sprint/week is complete the number will not change except for any update Team Settings.

Update in the following settings will change historical data

1. Retrospective page settings
   1. [Issue vs Story Points](#h_cd813559c8)
2. [Team settings](https://delivery.usehaystack.io/team/settings)
   1. Jira board
   2. Filter Sprints
   3. Members
   4. Show member's work outside of the board
   5. Include non-team members work

</details>

<details>

<summary>How is sprint completion calculated?</summary>

You can read how Sprint Completion Rate is calculated [here](#h_644d874c5f)[.](#h_87798c72d7)

</details>

<details>

<summary>Can I update the sprint completion calculation?</summary>

No. Sprint Completion metric is pre-defined. It cannot be configured.

</details>

<details>

<summary>Can I use issues instead of story points (or visa versa)?</summary>

Yes, you can switch between story points & issues. You can read more [here](#h_cd813559c8).

</details>

<details>

<summary>Can I use JIRA's original time estimate field?</summary>

No. Haystack only supports issues & storypoints. You can read more [here](#h_cd813559c8).

</details>

<details>

<summary>What is Injected Issue?</summary>

There are 2 terms you need to be aware of

* **Committed Issue:** Any issue that was inside the sprint before the sprint started.
* **Injected Issue:** Any issue that was added to the sprint after the sprint started.

**Note**: To handle edge cases, after a sprint has started, if any issue has been added to the sprint with-in a 10 minute period, Haystack considered them as "Committed Issues". After this grace period ends, all issues added the to sprint will be counted as "Injected Issue"

You can read more [here](#h_5970b5143a).

</details>

<details>

<summary>What happens when removing tickets from a sprint?</summary>

A ticket can only be removed from a sprint only during the sprint.

This would effect any metric from scope/completion rate/issue completed etc. for that sprint. Once the sprint is completed, the metrics will freeze.  \
\
For more info read [#h\_d7a2e62e6a](#h_d7a2e62e6a "mention")

</details>


---

# 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://help.usehaystack.io/features/retrospective.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.