What should a Development Team do when they struggle to deliver a work increment?

The emphasis on completing what the Development Team can within the Sprint and discussing any undone work during the Sprint Review is rooted in the principles of transparency and accountability in Scrum. It reflects the idea that the Scrum framework values collaboration and communication, particularly around progress and challenges faced.

By choosing to complete whatever work they can, the Development Team maintains their commitment to producing a potentially releasable product increment by the end of the Sprint. This dedication to delivering value, even when facing struggles, upholds the iterative and incremental nature of Scrum.

Additionally, discussing any undone work during the Sprint Review allows the team to provide transparency about their performance and the obstacles encountered. This conversation provides an opportunity for stakeholders to understand the status of the project, the reasons for any incomplete tasks, and to collaborate on future steps, ensuring continuous improvement rather than placing blame.

This approach fosters an environment of learning and adaptability, crucial in Scrum, as it empowers the Development Team to reflect on their practices and explore solutions collaboratively rather than becoming static or disengaged.