Skip to main content

How product owner share state of the backlog?

Last post 03:51 pm September 21, 2018 by Blethed Interruptions
2 replies
11:53 am September 21, 2018

Hi, I am curious how do you interpret and execute statement that ‘At Sprint Review the product owner shares the current state of the backlog...’.

My experience is that backlog is long list of stories, tasks, feature requests and/or bugs. I wonder how to share that state? 

Thank you 


12:27 pm September 21, 2018

My experience is that backlog is long list of stories, tasks, feature requests and/or bugs. I wonder how to share that state? 

That's correct, the Product Backlog can be a long list and it can contain all sorts of work. Just sharing the artifact itself may not therefore be enough to ensure that an understanding of its state is shared.

The Product Owner might need to identify changes made since the last Sprint Review or to summarize upcoming goals and pieces of work, for example.


03:43 pm September 21, 2018

@Ian I've tried this but the Product Owner said, "I can't remorse the anymets."  What should I do?


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.