Product Backlog and Goal
Level 2 Β· Scrum
What the Product Backlog is, how it is ordered, and why the top is clear and the bottom is rough. How the Product Goal gives the whole list one aim.
Course contentsLesson 5 of 19
Level 1 Β· What agile is
Level 2 Β· Scrum
Level 3 Β· Kanban
Level 4 Β· Stories, sizing and tracking
Level 5 Β· Other methods and scale
After this lesson you can
- Say what goes on the Product Backlog
- Explain why it is ordered, not just ranked
- Use the Product Goal to judge an item
10 mincovers 2 glossary entries
Worth reading first: Scrum Team and Roles
What the Product Backlog holds and what the Product Goal is
The Product Backlog is the ordered list of everything that might improve a product. It is the team's only source of work. The Product Owner keeps it in order. Items at the top are small and clear enough to start in the next sprint. Items near the bottom can be one-line ideas. A list of 200 items is normal.
Ordered means each item has one place, from first to last. There are no ties and no ten items all marked urgent. If two things both matter, one still has to go first. The order says what the team will work on next.
The top of the list gets the most care. The team splits big items into smaller ones, adds detail and sizes them, so the next sprint can start fast. The guide says this goes on all the time. The Developers who will do the work size it.
The Product Goal is the long-term aim for the product. It sits in the Product Backlog, and every item on the list should help reach it. A food delivery app might set a goal of half of all orders placed in under a minute. The team works on one Product Goal at a time.
The goal gives the Product Owner a way to say no. An idea that does not move the product toward the goal goes to the bottom, or off the list. When the goal is met, or turns out to be the wrong one, the team picks the next.
In the guide, each list carries one commitment. The Product Backlog's commitment is the Product Goal. The other two parts of Scrum that hold work carry one each too. A list with no goal is just a pile of requests.
The common mistake is a backlog that only grows. Ideas pile up at the bottom for years, and nobody reads them. Clear out what will never be built. A short list that is honest is worth more than a long one that is not.
Worked example
Emma says no with the goal
Emma is Product Owner for a library app in Vienna. Her Product Goal is that readers can borrow an ebook in 3 taps.
A request for a reading chat room arrives from a manager. It does not help the goal, so it goes to the bottom of her list of 140 items. A faster sign-in moves to the top.
The words for this lesson2
Check yourself
Why does the Product Backlog have a Product Goal?
Finished this lesson?
Marking it complete also marks its 2 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.