What should a Development Team do with unfinished work at the end of a Sprint?

At the end of a Sprint, the Development Team should engage in a discussion about unfinished work during the Sprint Retrospective. This is a dedicated time for the team to reflect on the Sprint, discussing not only what went well but also what didn’t. By addressing unfinished work, the team can analyze why it wasn't completed, identify any blockers or issues faced during the Sprint, and contribute to continuous improvement.

This dialogue fosters transparency and helps the team make informed decisions on how to handle similar work in the future. They can discuss whether to attempt the unfinished work in the next Sprint, how to adjust their processes or estimations, and what changes might be necessary to avoid similar outcomes later on.

Engaging in this review process is crucial to evolving the team's practices and ensuring that they become more efficient over time, rather than ignoring issues or making arbitrary decisions about the work.