Sprint Reporting - Planned Vs Actual

[Lee Street]

I'm looking to report on each Sprint, what the team actually planned vs what they actually complete of that planned work

Im not looking to do this manually, Im looking for a automatice report which states

Planned 50

Complete 30 of the planned 50

Did not complete 20 of the planned 50

Pulled in 25 (within the Sprint)

Complete 20 of the puled in 25

Did not complete 5 of the pulled in work

The outcome I'm looking at is Sprint Predictability and throughout against the Sprint goal

[Zane eazyBI Support · Accepted solution]

Hi @Lee Street

If you woudl like to analyze Sprint completion or how well the team keeps the focus on the committed tasks or Sprint scope changes (and what has changed) you might consider 3rd party app eazyBI for Jira.

For example, you can build a sprint balance analytics to see how many committed issues (or Story points) were completed and how many committed issues (or story points) were replaced with new issues (story points).

Sprint balance report and other Sprint analytic options you can check out in the eazyBI Demo account: https://eazybi.com/accounts/1000/dashboards/16272-agile

Best,
Zane / support@eazyBI.com

[Nicole Martinez]

The percentage this report shows is wrong.

[Zane eazyBI Support]

Hi @Nicole Martinez
The Sprint issues balance report shows three separate columns representing the count of issues, not the percentage.

• The first column shows a count of issues included in the sprint and highlights how many of them were committed how many were added later. 
• The second column shows a count of issues at the end of the sprint and how many were resolved or unresolved.
• And the third column shows the count of issues originally committed and also completed in the sprint. This bare will be shorter than.

[Nicole Martinez]

Thanks - this is very helpful!

I see 100% showing in the third column, over a bar that is lower.   

Can you tell me what each of the hover percents mean?

[Zane eazyBI Support]

Thank you for the screenshot to show where you see the percentage. Now I see where you got confused. It is default functionality to show the value of each column and the percentage of that column composition when hovering the mouse over the chart.

Fo the first column, there is the percentage of committed vs. committed and added. The third column shows 100% because committed of completed is the only value in that column.

You might enable data labels showing values with issue count on the bars so other users would know what to focus their attention on.

[Andrew Sear]

Hi, I had to extract the sprint report from numerous teams as a json file. Then I could summarize the data for each sprint, merge all the sprint files together, then import in Tableua to generate reports.

1. I manually entered teh URL for sprint reports, which returned json data.

2. Python script to summarize and merge data 

3. Save data as new JSON file

4. Import JSON file into Tableua.

I then had the number of Stories, Tasks, Bugs etc.. added to each sprint, completed, removed, and Story Points for same items. I could calcualte churn rates, predictability, graph against planned v achieved etc...

[Trudy Claspill]

The built-in Velocity Chart (available under Reports for a scrum board) shows Points Committed vs. Completed for multiple sprints. Doesn't this meet your need?

[Lee Street]

To my understanding, no.

It does not show if the original 100 story points were the 100 we complete

Thank you though!

[Daniel G_ Sinclair]

Also, this velocity chart is only for one board, right? I need to see numbers across projects and teams in a rollup.