Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Story Points for closed sprints

Matt O_Toole May 8, 2020 edited

I've read the linked article. Complex. I'm just interested in updating the SPs for completed issues in an old sprint, whilst another sprint (2 sprints - 3/4 weeks later) is currently running. This is simply so we can update the Velocity report in JIRA in order to get an idea of the team's average velocity.

I'm still a little unclear as to the potential ramifications in doing this. Does it mess up the Velocity Report chart? Will I see two instances of the old sprint, e.g., in the chart? Similarly, will the Burndown chart update correctly?

1 answer

0 votes
Siddharth October 9, 2020

I am also interested to know, if above can be done. Matt has a valid point. It helps to know the Velocity. 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 to Matt's point ( assuming I am getting it right) 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, 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?

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Atlassian Community Events