[Mythbusting] What Happens To The Sprint Backlog Items That Are Not Done?

What happens to the Sprint Backlog items that are not "done"? Does it automatically get carried over to the next Sprint?
#scrum #agile #backlog

[@scrummasterinblack]

Should the development team take overtime to ensure every Sprint Backlog items are "done"?

[@muchammadnurwibowo8255]

Dari semua jenis konten, myth busting paling ditunggu! Even ngalahin 2 mins FAQ

[@sakshisrivastava5959]

It was very helpful A big like for your video!

[@scrummasterinblack]

Thanks for watching.

[@alebigna]

Crystal clear and very useful! Thanks!

[@osnyzinho]

great video! thanks for sharing! When you visit Brazil, we will go drink some coffee!

[@michaelrealista6259]

Thanks this is very easy to understand.

[@Vikki1912]

Thank you for the video! I have a follow-up question: what to do with estimations (Story Points)? I know that some teams prefer to split a User Story into 2 parts ( Done and Not Done) in order not to lose the spent efforts ( Story Points) and re-estimate the part that goes back to Product Backlog. Another option is to re-estimate the original item in the backlog. What would you do in a such situation?

[@scrummasterinblack]

Viktoriia Titovchenko both are good approaches as long as the team owns it. Take it back to the team.

[@Tirn0]

Another option is to do neither. You only get the full value of the original estimate when your originally estimated story is done

[@betelhemabate4628]

very useful, thanks

[@scrummasterinblack]

Thanks for stopping by 🙏

[@budi0580]

👍 awesome 👍

[@thiagopereiradossantos588]

I'd like to know how to use nexus frameworks with kanban? Each teams there is a difference board?

[@scrummasterinblack]

Hi. In general yes, each Scrum teams should have their own Kanban board. They should also have a Kanban board to visualise the whole integration.

[@simonsimon2463]

What to do the completed sprints? and the completed issues in it?

[@scrummasterinblack]

Hi. As I share on this video kzbin.info/www/bejne/rInNe2huntCmgLM , any Product Backlog item that meets the Definition of Done can be released to the production environment.

[@simonsimon2463]

How to carry over multiple issues all together rather than pulling them 1 by 1? Thank you

[@scrummasterinblack]

What's wrong with pulling it one by one?

[@asksimon9813]

@@scrummasterinblack 10 times slower

[@scrummasterinblack]

@@asksimon9813 pulling one work at a time is 10x slower than pull multiple work at once? 🤨

[@asksimon9813]

@@scrummasterinblack yes if sprint has 10 issues to carry over out of 15 for example (1st sprint with all the team together)

[@simonsimon2463]

What do you to issues that need to be carried over to next sprint? Pull them in the next sprint log or create new ones?

[@scrummasterinblack]

The answer is on 2:54

[@scrummasterinblack]

I personally prefer "not creating new one" because I want to track the cycle time trends which is useful for forecasting as explained on this video kzbin.info/www/bejne/jYeoeYquetOcosU

[@simonsimon2463]

@@scrummasterinblack Sorry I forgot to add the words "on Jira"

[@scrummasterinblack]

Sorry mate. I don't use JIRA 🙈

[@ubinair4390]

@@scrummasterinblack Oh, I'm curious to know what software do you use?