Skip to main content

Scope of Sprint backlohg

Last post 07:50 pm April 25, 2017 by Benjamin D’Eusanio
1 reply
03:31 am April 16, 2016

Hi All,

I have gone through the scrum guide and other tests multiple times,but I couldn't get clear idea on below statements from scrum guide.

Development team collaborate with the product owner to negotiate the scope of sprint backlog within the sprint and development team can change sprint backlog through out the sprint??.

As per my understanding dev team can change the tasks/work in sprint backlog but guide says sprint backlog can be changed through out the sprint..can any one explain me this in detail.

Also what s the scope DEv team and PB negotiate?

Thank you


05:00 pm April 24, 2016

Hi,



In fact, the Sprint Backlog is a list of tasks + a plan to deliver the done increment.



It is possible that the PO has new important need which improve the value proposition of the product.

In this case, the PO asks the Dev Team if they think that the could handle these new tasks.

This is a conversation, not orders, the Sprint backlog is an artifact that is solely up to the Dev Team, but the PO can influence the Dev Team.



Before adding the new tasks to the Sprint Backlog, the Scrum Team has to think about the sprint goal, do the new tasks endanger it? That's why we are talking about a Sprint backlog scope that is negotiable.



Have a nice day


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.