Now that I’ve finished my series on the agile business analyst, I thought I’d turn my attention to exploring some of the fundamental aspects of product ownership in more depth.
My choice for the first topic – product backlogs – was inspired by Joshua Arnold who pointed out that the definition of backlog on AgileAlliance.org is a little… outdated.
He was right.
So in my role as Agile Alliance content curator, I started working on an update to the entry. As part of that effort, and perhaps in a fit of productive procrastination, I took a look around to see what else is out there about the product backlog.
I’ve included five of the resources about the product backlog that I ran across during my searches below. Each resource provides a different perspective on this fundamental concept. Those different perspectives can be instructive as you try to determine how to best use your product backlog.
I’d also like to hear what you want to know about product backlogs that may not be covered in those other resources. Put your burning questions about the product backlog in the comments.
Scrum Guide description of product backlog
No list of resources would be complete without the “official” definition of product backlog contained in the Scrum Guide.
The product backlog: your ultimate to-do list
Here is Atlassian’s look at the product backlog along with terminology slanted toward their backlog management tool – Jira. There are a couple of good points in here about how to keep your product backlog manageable.
10 Product Backlog Tips
Working with the product backlog can be challenging. If you find yourself wrestling with overly long and detailed backlogs, you may find this blog post from Roman Pichler helpful. In this post he provides ten practical tips that help you work with your product backlog effectively.
The new user story backlog is a map
How to stock the product backlog
In this post I describe the process I go through to stock a product backlog with product backlog items focused on delivering a particular feature.