Modify story points commited of a finished Sprint

[Mari Cruz Martinez Dengra]

Hello,

Every 2 Mondays a new Sprint is started, so it is closed the previous Sprint the same day.

It seems like for the previous Sprint, by mistake, it was started with no tickets, so no 0 story points, but such Sprint scope was modified right after starting it.

Today, once closed the previous Sprint, I see 0 story points committed, which does not really represent the reality.

💡 My question here is: is there any way to modify the story points committed for a closed Sprint? if so, what steps should I follow?

Thanks!

[G subramanyam · Accepted solution]

Hi @Mari Cruz Martinez Dengra  welcome to the Atlassian community.

Please be informed once a Sprint is closed, its closed and no modifications can be made in terms of estimations or reports.

Please go refer this document on velocity chart for more information.

And if you ask any work around? Yes, their is.

1. I would suggest get your "Jira admin" in the Sprint start meeting and ask him to cross check your Sprint Jira board with estimations.
2. Take a screenshot.
3. Ask him/ her to start the Sprint on your behalf.
4. After a day or two in the Sprint, explore Jira reports: Sprint, Velocity, Burndown etc to have a look at how they are reflecting the team data.
5. Finally, get your "Jira admin" on the Sprint closure meeting and ask him/her to cross check your Sprint Jira board with estimations, end the Sprint on your behalf.
6. Now explore the reports again to get a view of data.

Now if you still see the committed points to be "0", then your Jira admin should identify the underlying problem and fix it.

[Trudy Claspill · Accepted solution]

Hello @Mari Cruz Martinez Dengra 

Welcome to the community.

It is not possible to change the Committed Story points after a sprint has been started or completed.

[Mari Cruz Martinez Dengra]

Is there any workaround when it is done by mistake? we are using the velocity chart report and having 0 story points sounds weird.

Thanks for your response

[Trudy Claspill]

If you detect the problem while the sprint is in progress, I would recommend creating another sprint, moving all the issues to it, and then starting that new sprint after moving the issues. The original sprint could then be deleted.

The same might be done for a completed sprint (create a new sprint, move all the issues, start and complete the new sprint, delete the original sprint). I have not tested this, so I can't say with certainty how it would affect your Velocity report. You should try it out in a separate test project with test issues first.

[Brent Stone]

I have a team member who tends to add stories into the sprint a few hours after it has been started.  I go to the backlog view, click on "edit sprint" and change the start time to later in the day to align with after he has added his stories.  This corrects the starting/committed value to include all the stories he added after starting the sprint.

[Brent Stone]

I have a team member who tends to add stories into the sprint a few hours after it has been started.  I go to the backlog view, click on "edit sprint" and change the start time to later in the day to align with after he has added his stories.  This corrects the starting/committed value to include all the stories he added after starting the sprint.