Back to Forum

What Scrum Master should do if defined work is not done at the end of the Sprint?

Last post 11:32 am August 18, 2019 by SUMIT AGRAWAL
2 replies
SUMIT AGRAWAL
07:32 am August 18, 2019
Thomas Owens
10:12 am August 18, 2019

First, ask if the Sprint Goal was met. Meeting the Sprint Goal is far more important than completing all of the work that was put into the Spring Backlog.

Then, the Scrum Master should facilitate the Sprint Review and Sprint Retrospective as necessary. The Sprint Review, among other things, gives a chance for the Product Owner to share with stakeholders the reality versus the initial forecast - what work was done and not done - and the Development Team to discuss things that went well and what problems arose during the Sprint. The Sprint Retrospective gives the Scrum Team a chance to inspect itself and its way of working to improve for the next Sprint. As a result of these two events, the Scrum Team should have a reordered Product Backlog that reflects the most valuable work to be done for stakeholders and a good idea of how to improve on their ability to deliver in the next Sprint, both of which provide feedback into Sprint Planning. The team can ensure that they craft an appropriate Sprint Goal and select an appropriate amount of Product Backlog Items based on what they've learned and what they are forecasting for the upcoming Sprint.

SUMIT AGRAWAL
11:32 am August 18, 2019

Thank you Thomas for the response.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.