3 strategies to deal with Sprint carry over in a Scrum Team

Carry over is inevitable. Is it good or bad?

Watch the video to find out how to deal with Sprint carry over and how to avoid it in the future.

In this video I talked about:
✅ Why having carry over is neither good or bad
✅ Whether you should re-estimate your carry over
✅ Should you put it into the next Sprint or not

and more!

◼◼◼◼◼

Resources mentioned:

◾ ◾ ◾ ◾ ◾

◾ ◾ ◾ ◾ ◾

✨ MY FAVORITE TOOLS ✨
Use my referral links to get some sweet bonuses

◾ ◾ ◾ ◾ ◾

👋 Follow me and ScrumMastered on social media:

❗ DISCLAIMER
If you are using my affiliate links I will make a small commission on the sales made. This has no additional cost to you.

⚫ CHAPTERS⚫
0:00 Introduction
1:32 Why it’s bad to have carry over
2:24 Why it’s ok to have carry over
4:14 To re-estimate or not to re-estimate
6:06 Next Sprint or Product Backlog
8:08 How to avoid it in the future?
8:33 Strategy 1: Sprint Planning
9:40 Strategy 2: Splitting work
10:57 Strategy 3: Updating your Sprint Backlog
12:14 Summary

[ScrumMastered]

I hope this video was helpful.

📖 If you need help facilitating a working agreements workshop, you can use this guide:


📩 Subscribe to my newsletter to get updates on new stuff and special offers:

[salyuk]

Thank you 👍 Very valuable information and advice!

[alebigna]

Hi Daria, happy new year! This is a super great and most useful video! Loved it! It clarifies a lot of things about this subject and I agree with you on all the points you've done!
I wish that, sooner or later, I would be able to work side by side with an experienced SM like you or, a dream :D, with you!!!! It would be a great booster for my skills and competencies!
Regards, Alessandro

[labi]

Happy New Year.
So should we re-estimate, what is left of an uncompleted work? How is that determined? The Team does this once in a while. I frown at it but I don't want them feeling demotivated or feeling bad that there's no value accepted for the work that has been done in the prior sprint.

[Cromfeld]

Considering the fact that the PO is responsible for the ordering of the product backlog. I would carry it to the next sprint as a PO with reestimation. I had this same issue as a dev, when the team dragged a huge feature through sprints. It was not pleasant.

[yagpat]

Thanks Daria for wonderful video.

How to find an accurate velocity when you have incomplete user story carried over to next sprint? (As most of the work done in the previous sprint)

[amea]

Hello, thanks for this video, it’s very interesting. I have a question about re-estimating the remaining work at the end of a sprint. Let’s say my team hasn’t completed a product increment estimated at 8 story points; after discussion, the team decided to put it in the next sprint to complete the work, is the new estimation done on the remaining work only or should it consider the work in its entirety by considering what the team learned from the previous sprint? Thanks in advance

[athaleta]

If you reesimate based on the effort left and not taking the "busy work" in the estimation, does it mean that your velocity from the last sprint is not showing the real work or you won't see this busy work as part of the velocity since there is no increment created? Thank you! :)