Unfinished User Stories should not be demonstrated during the Sprint Review. The unfinished User Stories should go back to the product backlog, be re-estimated, and considered for the next Sprint. Re-estimating the user stories ensures that the future work is true to the point estimate. The work performed during the current sprint is “lost” as far as the worked points. Following this process will avoid assuming that every Sprint will have rollover stories and that the stories will remain a priority from Sprint to Sprint.
Should we move unfinished User Stories forward to the next sprint?
Updated: May 15, 2023
Disagree. Re-estimating would not allow you to get better at estimating. Automatically putting it on the backlog might incentivize developers to run out the clock on stories they hate. Would rather have the team focus on getting the story over the finish line and meeting the sprint commitment.
Unfinished user stories might go back to the pbl only if the po still deems them valuable.