Back to Forum

[Re-posted] Who can change the Sprint Backlog?

Last post 02:34 pm May 14, 2021 by Ankush Bhatia
3 replies
Thiều Đức Minh
04:13 am May 14, 2021

Hi guys,

I read some similar topic, but not clear to know.

In my opinion, Developers can change plan to achieve the Sprint Goal, PO may be update content as information for Developers to understand.

Thanks,

Scott Anthony Keatinge
05:38 am May 14, 2021

PO owns & orders the PB.  PO & Developers refine the PB. 

Scrum Team decide on sprint goal based on current product goal, and what the PO would like to achieve that sprint. 

Developers select PBIs from PB that will help them to achieve the sprint goal.  These are usually PBIs from the top; however, due to dependencies, they could also be from anywhere in the PB.  PBIs selected could also help the scrum team improve their own effectiveness. 

The SB is owned by the Developers; therefore, it is them who can change it. 

The scope of the sprint can be changed if necessary via negotiations between the Developers and the PO. 

Ian Mitchell
06:26 am May 14, 2021

The Sprint Backlog has a forecast of valuable work from the Product Backlog and the Developers' plan for meeting the Sprint Goal. The Product Owner manages the Product Backlog and understands its value. It would therefore be wise for Developers to collaborate with the Product Owner regarding any changes to selected Product Backlog items. 

Ankush Bhatia
02:34 pm May 14, 2021

Product Backlog is owned by PO as he is accountable for maximizing the product value. Developers works on Sprint backlog which has prioritized items from product backlog. Developers create a plan as how to convert that into incremental value hence they have every right to change the plan keeping the Sprint goal intact. However, they should (I would say must) work with PO to make any changes in the plan. This is to ensure everyone is on the same page.

 

 

 

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.