What should be done between two sprints?
Each Sprint that a Scrum Team does is an opportunity for learning through “inspect and adapt”. If there is a break or a pause between Sprints, the Scrum Team may forget what it has learned or fail to apply that learning in a timely manner in the next Sprint.
Who can extend sprint duration?
Changing the sprint length is a decision best taken by the Scrum Team, in the Scrum Retrospective, before starting the next sprint. This decision can be temporary (only for the next one or two sprints) or permanent (for every sprint from that moment on).
What to do when a story is incomplete in a sprint?
Whenever your team finds an incomplete story at the end of the Sprint, simply roll that story, in its entirety, into the next Sprint. When this happens, no points should be awarded to the team, for partial completion of the story. Furthermore, I recommend that teams do not re-estimate the remaining effort of the story in the next sprint.
When to move unfinished stories to the next sprint?
You should never automatically move an unfinished story to the next Sprint. You should first move it to the Product Backlog where it will go through prioritization (again). Why should you move it the Product Backlog first? The Product Owner is responsible for prioritizing the Product Backlog.
What should you do at the end of a sprint?
While there is no universally-agreed-upon guidance for how to handle this, here is an approach that I’ve found that seems to work well for most teams. Whenever your team finds an incomplete story at the end of the Sprint, simply roll that story, in its entirety, into the next Sprint.
Why was there a Sprint Backlog refinement meeting?
At Steve’s suggestion, the Team delayed the Sprint to have a Product Backlog Refinement meeting. The result was that all User Stories at the top of the Product Backlog were properly discussed with the Product Owner, Stories that were too large were split into smaller ones, and all the Stories now have estimates.