Accounting for Story points after sprint is closed

[Siddharth]

Is there a way to see velocity for completed sprints, if I update the SP(Story point) for the issues after they have been closed in the corresponding(closed) sprint?

Granted that, SPs are to be entered before sprint starts and it is not encouraged to change the SP(Story point) during and after Sprint. But if team has introduced new basis of estimate and would like to see historically how team would have performed if this basis was estimate had been in place, this would be good to know.

Note: I understand we can simply edit SP value in any Jira issue after it is closed. But the updates do not get reflected in the Velocity report ( since the sprint is closed). Any work around?

[Bill Sheboy · Accepted solution]

Hi @Siddharth -- Welcome to the Atlassian Community!

As you noted, it is generally not helpful to change the estimates of story points once the sprint as started or completed.  Rather, the team could consider during the retrospective what happened (or they did not know) that led them to later want to change the sizing.

Regardless...the situation you describe where the team has changed their understanding of sizing leads them to want to resize.  What happens if they want to do that again?  Or again?  Editing Jira will lose the history from a point in time of how the team worked at that point in time.

As an alternative the team could export their Jira issue data to a spreadsheet, alter the sizing, and then re-create the velocity chart manually.  They would have the new information to review and would preserve the original data in Jira.

Best regards,

Bill

[Siddharth]

Thank you