Skip to main content

Product Backlog vs Sprint Backlog

Last post 03:09 pm November 3, 2017 by Joost Okkinga
6 replies
08:34 am January 14, 2014

Hi Guys,

I know that Product Backlog should contains user stories and is managed by Product Owner, while that Sprint Backlog the responsible is the Team.

1) This image is really a Product Backlog?

http://epf.eclipse.org/wikis/scrum/Scrum/workproducts/resources/product…

2) This image is really a Sprint Backlog?

https://www.scrum.org/portals/0/Images/Sprint-Backlog.png

Thanks for your response

Regards


08:40 am January 14, 2014

>>This image is really a Product Backlog? http://epf.eclipse.org/wikis/scrum/Scrum/workproducts/resources/product…

This looks like a reasonable example of a product backlog. I have no idea if it is a good well formed backlog however. I would need to see the detail that is on each of the PBI's. for that.

>>This image is really a Sprint Backlog? https://www.scrum.org/portals/0/Images/Sprint-Backlog.png

I would say no. It is a visual representation of the contents of a Sprint Backlog and not one itself. Think of the Sprint Backlog as those PBI's that you have agreed with the PO to attempt with a plan to complete them. So it is simply one or more PBI's broken down into a plan.

The most common form of a Sprint backlog is a bunch of tasks under each PBI.

Did that help?


08:54 am January 14, 2014

Hi nsanzana,



1) This image is really a Product Backlog?

http://epf.eclipse.org/wikis/scrum/Scrum/workproducts/resources/product…



There is no rule in SCRUM forbidding this to be a product backlog. It is ordered and estimated, so the team should be able to work with it.




2) This image is really a Sprint Backlog?

https://www.scrum.org/portals/0/Images/Sprint-Backlog.png



This is a symbol picture of a sprint backlog. Of course a real sprint backlog needs content inside the rectangles: At least Descriptions and estimates for the PBIs and descriptions for the tasks.
Best, Ludwig


03:35 pm January 14, 2014

>This image is really a Product Backlog?

It would be...apart from the "By" attribute. This appears to show individual ownership of PBIs or their estimates. If either case is true, then that's not a Scrum Product Backlog. In Scrum the PBIs should be owned by the Product Owner, while the Development Team should be collectively responsible for estimates.

> This image is really a Sprint Backlog?

No. It looks like a schematic of a task board. The two states on the left (PBI and ToDo) may represent a valid Sprint Backlog if populating them is the output of Sprint Planning, and if they are regularly updated.



07:33 am January 15, 2014

I like to oversimplify it to help those who are still new to Scrum as such :

Product Backlog: list of things that needs to be done to make the product come into existence
Sprint Backlog: list of things that needs to be done in the current Sprint, which includes selected Product Backlog items


07:51 am January 18, 2014

Incidentally, a couple of years ago David Starr and Ryan Cromwell discussed exactly that taskboard image in the context of what should constitute a Sprint Backlog. You can read about it here:

https://www.scrum.org/About/All-Articles/articleType/ArticleView/articl…





10:17 am November 3, 2017

Thank you Nicolas for strating this useful topic. Unfortunately the link is broken https://www.scrum.org/portals/0/Images/Sprint-Backlog.png which makes it hard to follow. Would you mind fixing it? Yours -Joost


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.