WHY SCRUM TEAMS HAVE SPILL OVER / CARRY OVER ? | Aisha Scrum Tech

[@Susanchogwu]

Thank you for sharing, really insightful. I agree with you on all the points.

[@AishaTech655]

Thank you 🙏🏾

[@gifss99]

Can you please help me with the scenario below?
Issue/Story comes up when a story of 5 points is 90% done but needs a tiny bit more work in the next sprint. Usually we take that forward to the next sprint and finish it there. But the issue is in the sprint burndown (or epic, release burndowns) it shows that we did no work in the first sprint and over worked in the second sprint.
What's the solution?
Eg. Story - 5 points and left with 2 points of work. I'll move to next sprint bcz PO said it's high priority.
What we need to do for above scenario in next sprint ?
Please suggest 🙏

[@AishaTech655]

You will have keep the story point, you might velocity will be lower this sprint but when you close that story next sprint and take more work it will even out.

[@gifss99]

@@AishaTech655 Thanks for your reply. But do we need to move the complete US or clone/split the US when moving to the next sprint.

[@AishaTech655]

You move the complete US and not split it, as the story did not meet the definition of done.

[@emmanuellauchegbu564]

Amazing content. Very informative, valuable, and straightforward. Thanks for sharing. Keep it coming please ❤

[@AishaTech655]

Thank you for watching 🙏🏾🙏🏾🙏🏾

[@thecreativefamjoy]

Clear and unambiguous explanations, I agree with you 💯 on proper stories estimation to avoid spill over

[@AishaTech655]

Thank you for watching 🙏🏾🙏🏾🙏🏾🙏🏾

[@comradejalloh4473]

Very educative. I agree with you burnout can be a very serious issue for a team

[@AishaTech655]

Thank you, I totally agree 🙏🏾🙏🏾