nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint report vs Scrum Tracking

Pieter_p5krsi

When reviewing the data from the sprint review. I get a good overview of what has happened during a sprint. I can see how many issues were completed, tracked, ...

However, the scrum tracking also provides these insides, but some markers match, like the number of issues. But the number of resolved issues do not match, there is even a really big discrepancy. Also the number of story points do not match. Where is this discrepancy coming from and how can I best use these tools in my advantage when I went to calculate the capacity of the team from the upcoming sprints.

Accepted answers

All comments

Rebekka Heilmann (viadee)

Hi @Pieter and welcome to the Community,

not sure what "Scrum Tracking" is - a Marketplace App?

My best guess without knowing more details would be that one is based on columns and the other one on resolution/status:

Board Reports don't care for Issue Status or Resolution. For Boards the First Column/Backlog is "To Do" and the last one (on the right side) is "Done". So anything not moved to the Right column at the end of a Sprint is considered not done regardless the actual status (category) or resolution.

Pieter_p5krsi

Hi, thanks for the answer. On our jira 'Scrum Tracking' is situated under the 'Link Hierachy' section in our backlog.

The main reason I'm asking is because I want to track how much did the team do during the sprint, how many issues are unresolved and looks for a trend.

But the information doesn't always match. Is this because of issues that are then resolved in another sprint but not in the one it was initially put in? I also do not know why there is a discrepancy in the story points between the two.

Thanks

Danut M _StonikByte_

Hi @Pieter,

My recommendation is to use the Sprint report as a reference. For the discrepancies in "Sprint Insights", which I guess is the one you are referring to, you could open a ticket with Atlassian Support.

If the Sprint report is not easily accessible, you could also use the Scrum gadgets offered by our Great Gadgets app, which are reliable and more advanced, can include sub-tasks and work with any type of estimate. They include sprint burndown/burnup, release burndown/bunup with forecast, team velocity gadget and more.

See these articles:

https://community.atlassian.com/t5/App-Central/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063

https://community.atlassian.com/t5/App-Central/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694

Hope this helps.

Danut.

Rebekka Heilmann (viadee)

Then this is definitely a Marketplace App, I couldn't figure out which one though.

Again: Scrum Boards and their native Reports don't look fo resolved / unresolved, they only count the rightest column on your Board as "done".

Your App might use Resolution or Status for their Reports.

For Story Points it could be that the Board Reports don't count Sub-Tasks, while the App does?

It's hard to tell without seeing specific Data and without knowing what App you are using.

Pieter_p5krsi

Thanks for the answer.
I think for my purpose and the answers I received here I can best use the sprint report. The app didn't feel like market place but it was already there when I started using jira server at this company. I can not share specific data due to confidential information. But thank you!

Pieter_p5krsi

Thanks for the answer. I am really looking for data that only cover the sprint periode. How was it at the start and how at the end of the sprint. I do not care if the issues were resolved in the next sprint, because I'm trying to see what our capacity is during one sprint. So thanks, I think the sprint report will be my best reference.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-server