Close sprint with inprogress issue

Moti Stein

Every 3 weeks when I close the spring I left with few issues on QA/In progress that I want to move with the team to the next sprint (low priority issues).

 

But if the issue is 5 story points and most of the issue is completed (~3 of 5 story points completed) when I closed the sprint the whole 5 story points are not completed. and the graphs of velocity of the team showing that these issues are not working by the team.

 

What is the correct way to handle this? I mention few examples I think about.

Close sprint -> change story points -> start sprint

Change story points -> close sprint -> start sprint

Clone issues -> Done old issues -> close sprint -> update new story points -> start sprint

 

 

Trudy P Claspill

I agree with @Nic Brough -Adaptavist- 

In my opinion you need to look at why the stories are not getting completed in the sprint to which they are assigned and address that.

Is too much work getting assigned to the sprint?

Is work getting added to the sprint that is diverting efforts from the originally planned work?

Is the estimate of work effort not accurate?

You need to address the root cause of why the stories are not getting completed.

Maybe you need to break your stories into smaller scoped stories that can be fully completed within the sprint. Maybe you need to not let additional work get pulled into the sprint. Maybe you need to look at your effort estimating and work towards better accuracy.