simple-product-backlog-thumbnail

Simple Product Backlog Example

Screenshot of the simple Scrum product backlog
Links to the various product and sprint backlog templates used in Scrum are among the most popular pages on this site. While these templates are indeed useful, I believe, that during transition to Scrum too powerful tools can draw too much attention and force the team and Product Owner to learn tools instead of learning Scrum. The main point of the product backlog is to list the requirements in the strict and unambiguous order.

I created the very minimal product backlog template (XLS) for Scrum inspired by the Mike Cohn’s product backlog screenshot. You can use this Excel example as a template for your own backlogs. There are plenty of comments on the sheet to help you get started. Consider it published to public domain. It would be very kind of you not to delete the link to this site, but technically you are free to copy, reuse or even resell this example.

See Also

Good or Bad

What do you think? How good is this template for starters? Would you like to see more similar templates with the different amount of functionality?

9 thoughts on “Simple Product Backlog Example”

  1. Artem,

    Thanks for providing this simple template. I’m utilizing a modified version of the Scrum methodology for my senior project in college, and it looks like this will come in handy. I believe the template is simple enough that a small project can utilize it without hassle.

  2. I will be happy if this template happens to be useful for you, Nick.

    It would be great if at some point you could share your impressions on how useful the template is. Also I believe a lot of people would find it useful to examine how your real world backlog evolved over time.

  3. I am also in the process of doing thesis project and going to use some kind of simple Scrum for it and I hope your template will help in it.

    1. I prefer using one *product* backlog per one *product*, but that, certainly, can include the future releases and wish list-like features in the bottom. Actually Product Owners use a strategy of putting even crazy requests to the bottom of the product backlog. It will show that you care if request comes from e.g. your indirect boss, but you still won’t ever do it, because you know it will always be of the low priority 😉

  4. While these templates are indeed useful, I believe, that during transition to Scrum too powerful tools can draw too much attention and force the team and Product Owner to learn tools instead of learning Scrum. The main point of the product backlog is to list the requirements in the strict and unambiguous order.

Leave a Reply

Your email address will not be published. Required fields are marked *