Back to Forum

Changes to Sprint Backlog

Last post 09:51 pm January 5, 2017 by Ian Mitchell
3 replies
Nav Singh
10:45 am January 4, 2017

Hi,

I wanted to clarify my understanding of: changes to Sprint Backlogs.

As per my understanding, once the subset of User Stories (items) are selected from the Product Backlog, this now forms the scope of the Sprint Backlog. Once the Sprint Backlog is finalised, no new User Stories can be added to the Sprint Backlog.

In online quizzes i have got the following questions wrong:
1. Is it prohibited to add new work into the Sprint Backlog later by the Development Team?
I answered True (but the correct answer was False).

My Question: By "Work", does that mean "Tasks"? If so, I understand why the answer is False.

2. Who is allowed to make changes to the Sprint Backlog during the Sprint?
I answered "No-one", but the correct answer was "Development Team".

My Question: I thought that once the Sprint Backlog was finalised no changes could be made? Or are they referring to reducing Sprint Backlog scope only?

Thanks


Ian Mitchell
12:32 am January 5, 2017

What does the Scrum Guide say about changes to the Sprint Backlog and who is allowed to make them?

Nav Singh
10:22 am January 5, 2017

That only the Development Team can make changes to the Sprint Backlog during a Sprint.

I guess I was getting confused from multiple sources. I believe that only the Development Team can change the Sprint Backlog during a Sprint. Furthermore, they can even add/remove User Stories as long as it does not impact the Sprint Goal.

Ian Mitchell
09:51 pm January 5, 2017

Correct, although they may revise the Sprint Backlog to *positively* impact the Sprint Goal, in the sense of increasing their chances of meeting it.

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.