Do changes in story points affect previous sprint reports?

[michael.vogel]

After a sprint is completed stories are carried over where work has already been done. A 13 might have 5 story points work done already and 8 points left. If an additional 5 points of work are done and the story is carried over again, then the final sprint for that story will have 3 story points left.

So:

• sprint 1: 13 points estimate
• sprint 2: 5 points estimate
• sprint 3: 2 points

Are the reports of previous sprints modified every time the story points are amended?

If so, that should be a bug IMO as it messes with sprint velocity and forces users to keep track of the actual story points in some other manner, which introduces an easy way to make mistakes.

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

That is not how sprint estimates work.  In the case of your story that has 13 story points on it, and is the only story in all three sprints, then you have:

• sprint 1: 13 points estimate
• sprint 2: 13 points estimate
• sprint 3: 13 points estimate

You should not be amending the estimate, it breaks all the reporting (and yes, will break your old sprint reports)

[Rebekka Heilmann _viadee_ · Accepted solution]

Hi @michael_vogel 

Not - Sprint Reports are done and not updated once a sprint is closed.

Are you using time tracking on your issues? You could then see how much of it is still open at the end of a sprint. Then you would have the 5 SP work done reflected in your sprint report. However that only works properly when working with actual time (d/h/m).

You could also split the issue into two - giving the original one 5 and the other one 8 and moving the new one into Backlog. You then move the original issue to the Done Column. In you Sprint Report you will see that Estimations changed on the original one. Your velocity would be based on the 5 SP actually done within your Sprint.

[michael.vogel]

Hi @Rebekka Heilmann _viadee_

Thank you for your response. We currently do not use time-tracking in our issues.

If the Sprint Reports are not updated once a sprint is closed, what advantage would splitting the issue in two have?

[Rebekka Heilmann _viadee_]

You split the issue before you close the sprint, leave the original one in the sprint and create the new one in the backlog -> you'll find the option "Split issue" on right click in Backlog view.

Estimation is updated on the original issue and therefore updated in the Sprint report.

But: Because now you can close the original issue (because the part that hasn't been finished ended up in a new issue) the Sprint Statistics now calculate the Velocity correctly. Otherwise you will always loose those worked hours/efforts in statistics.

[Valeriia_Havrylenko_SaaSJet]

Hi @michael_vogel  👋

And welcome to the community! 

I wanna suggest you to try Sprint Performance Report where we have all the metrics for each sprint. You can see here added, removed, carryovered, completed and not completed Story Points as well. 

    

I would be happy if you had a look at it! 

Try Time In Status for Jira + Sprint Report for free.

You can also book a live demo - we'll show you the application inside out and answer all your questions.

Have a nice day, and happy sprinting 🥳