Carrying over points to a new sprint

[Chrissy Garnett]

If we have a jira in our sprint which is estimated at a 5. By the end of the sprint only 2 points of effort have been done on it. 

We don't lose that effort. But there appears to be no way capture that. You either pull out of the sprint into the back log and pull into the new sprint and re point. 

Or clone the Jira, add the 2 points in to the cloned Jira and put into Done, then pull the original into the backlog and pull into the new sprint and change to a 3. 

[Bill Sheboy]

Hi @Chrissy Garnett 

What do you mean by "We don't [want to] lose that effort"?  What problem are you trying to solve?

Typically when Scrum teams size work, they use it as a tool to form a shared understanding of the request and the work involved to deliver it.  When that practice is done consistently sizes could also be used to help forecast completion of future work, such as with velocity.

When at the end of a sprint some started items are not completed, that is great information for a team to take into a retrospective to learn how to improve planning.  However the requested item is not done.  For teams measuring velocity, there is little value in claiming "partially done".  Instead the team could consider the impact on capacity if that work continues into the next sprint's backlog.

Kind regards,
Bill

[Chrissy Garnett]

Thanks Bill,

We do measure velocity and when we demo to our stakeholders We explain how may points we estimated and how many we achieved as a team. 

However, there are times where we have to carry over Jiras into a new sprint because of X reason. So because the Jira was started some effort has already been given. 

On Classic Jira you used to be able to Split the Jira. But can't see this function in Next Gen. 

[Bill Sheboy]

That splitting feature appears to be an open suggestion for team-managed projects, which you can vote for/watch to see progress here: https://jira.atlassian.com/browse/JSWCLOUD-18452

[Chrissy Garnett]

Thanks Bill