Skip to main content

Sprint Backlog

Last post 09:53 am April 19, 2018 by Ian Mitchell
2 replies
11:25 pm April 18, 2018

<Only the Development Team can change its Sprint Backlog during a Sprint>

In case if PO wants to change the PBI in the sprint backlog, can PO change it or is this a freeze period.


12:25 am April 19, 2018

If the PO wants to change what have been forecast at the sprint planning, a conversation between the PO and the Dev Team must occur. Will the changes endanger the sprint goal? Not started PBI in the sprint could be interchanged with more important requirements as a result of the conversation.


09:53 am April 19, 2018

If the PO believes that the plan for achieving the Sprint Goal would be improved by changing Product Backlog items, then he or she ought to advise the Development Team accordingly. They can then make an informed decision.

Bear in mind that a Product Backlog item ought to leave room for discussion during the Sprint. For example a User Story, as a placeholder for a conversation about a possible requirement, should be compliant with the INVEST criteria and thus negotiable to some degree.


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.