Retrospective
Learn how to use the retrospective page
Last updated
Was this helpful?
Learn how to use the retrospective page
Last updated
Was this helpful?
This blog will go over how to use page in Haystack.
Note: Retrospective page has different views for Kanban & Sprints boards. The Kanban version will be a trimmed down version of the Sprint one.
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.
Note:
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
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
.
Note:
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
For Kanban teams it's end of week, for Sprint teams it's end of Sprint
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
Note:
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.
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
Note:
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
For Kanban teams it's end of week, for Sprint teams it's end of Sprint
You can click on any week/sprint and drill-in into that specific report.
You can check more about Retros Report
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.
Issues Calculation: Issues that are tagged as commited or injected
Points Calculation: Points of Issues that are tagged as commited or injected
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.
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
Opens Release notes for that sprint.
You can change all calculations to
Issues
Points
where Points represent Story Points
field in JIRA.
The setting will effect on the following metrics
You can export Retro Report in CSV format using the Export button.
You can export Retro Report Drill-in page in PNG format using the Export button.
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}
Completion Rate metric changes based on.
You can check every issue that was included in the calculation by
You can read more about
Issue Completed metric changes based on
You can check every issue that was included in the calculation by
You can read more about
Scope Change metric changes based on
You can check every issue that was included in the calculation by
Investments metric changes based on
Learn how to
You can check every issue that was included in the calculation by
You can read more about
In Jira you can set . You can see the goals set in Jira inside Haystack.
Read more on
Clicking on "See details" button will show a with every issue that Haystack used to calculated this metric.
Issue Completed metric changes based on
Clicking on "See details" button will show a with every issue that Haystack used to calculated this metric.
Read more on
Clicking on "See details" button will show a with every issue that Haystack used to calculated this metric.
Learn how to
Clicking on "See details" button will show a with every issue that Haystack used to calculated this metric.
Read more on
See for a broader view
See for a broader view
The in Retros page is the only week/sprint that is not completed, thus any number you see there can change during the week.
The report will stop being as active and the tag will be removed. Any number you see will freeze unless you change .
Except for the , all numbers are static.
You can read how Sprint Completion Rate is calculated
Yes, you can switch between story points & issues. You can read more .
No. Haystack only supports issues & storypoints. You can read more .
You can read more .