Scrum Primer - Product Backlog

This article is part of a series on Scrum Primer. See the first post on Sprints

As per the Scrum Guide, the Product Backlog is an emergent, ordered list of needed improvements to the product. It is the single source of work undertaken by the Scrum Team.

The organisation may already have a product roadmap to build a product based on business strategy and priorities.

Product Backlog

The backlog captures all of the requirements for the product's features as User Stories. Each User Story must be assigned an estimate, business priority and status.

The Product Owner owns the Product Backlog. At times, the backlog would require grooming called Product Backlog Refinement

Tips

Avoid oversized backlogs - it's only for stories and categories like epic stories that it belongs to. Don't clutter it with Scrum Board To-Dos and Feature descriptions.

Keep it organised - Keep it organised and easy to read. The advantage of Agile is the inherent transparency it provides to everyone involved. You shouldn't need to run a training session to educate someone on how to read a Product Backlog.

Take note of dependencies - Find a method to note dependencies among backlog items.

Schedule Backlog Refinement activities - though not a must but is recommended that you have this regularly scheduled especially when your team is just starting on Scrum.