Moving unfinished stories to future sprints or the backlog moves the points too.

ldeveney
Giga Contributor

Hi...

Moving unfinished stories to future sprints or the backlog moves the points too. Is this behaving as designed? Is there a way to preserve the original point total for a sprint (before moving the unfinished story) to determine success of the sprint?

Linda

1 ACCEPTED SOLUTION

Thom12
ServiceNow Employee
ServiceNow Employee

Linda, also know that what madhuumapathy described (introducing a new column like CommittedPoints and saving the sum of the estimates on all of the stories in the sprint to CommittedPoints when you start a sprint) is something that's likely to become out-of-the-box functionality starting in New York. We can then leverage that data to provide insights like historical views into team predictability.

 

View solution in original post

8 REPLIES 8

Madhu80
ServiceNow Employee
ServiceNow Employee

Hi,

When closing a sprint, moving unfinished stories to the next sprint or backlog is behaving as designed. As to preserving the original total points on the sprint, one way to achieve that would be to introduce a new column and copy the value of the total story points to the new column when the state of the sprint changes to Current.

trishjohnson
Kilo Guru

Not an answer so much as food for thought... 

 If it's an untouched story, then no problem moving it as no risk losing the points.  You'll show the moved points in burndown.

If the story is UNFINISHED, then you want to capture the work in pts you've done in the current sprint, plus get the story into the next sprint easily, right?

We put an Insert and Stay rule on the story and create that duplicate story in the next sprint, close out the current and take the duplicated story and edit it to remaining work with correct points.

This may seem like a lot of management, but if you're truly trying to capture the points, it's the most accurate with least effort we've found. 

You also can start getting a handle on what is falling out in your daily's so that you can Insert & Stay>Tag to Next Sprint>Edit story in time for sprint planning.  ...sometimes. 

No, it's not perfect but it works! 🙂

Hi @trishjohnson - is this something you still practice? Any updates or process improvements? - I am dealing with the same thing, and it seems there has to be a better way to track now that there are a few more releases behind us since you last posted this.

Thom12
ServiceNow Employee
ServiceNow Employee

Linda, also know that what madhuumapathy described (introducing a new column like CommittedPoints and saving the sum of the estimates on all of the stories in the sprint to CommittedPoints when you start a sprint) is something that's likely to become out-of-the-box functionality starting in New York. We can then leverage that data to provide insights like historical views into team predictability.