Product Backlog & Product Goal

PSM I PSM I · Artifacts & Commitments

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. Three words in that definition carry the whole concept. Emergent means the backlog is never finished: it evolves as the product, the market, and the team's understanding change, and it is never a complete upfront specification. Ordered means every item has a place in a sequence decided by the Product Owner, with the most valuable work at the top. Single source means there is one backlog per product — not one per team, not one per department, and not a separate list kept by a manager. If work is not in the Product Backlog, the Scrum Team is not doing it. The exam tests this definition relentlessly, because in real organizations the backlog is constantly undermined by side lists, executive requests, and shadow priorities.

Each Product Backlog item carries attributes that vary with the domain of work, but typically include a description, an order, and a size (an estimate). Items at the top of the backlog are usually smaller and more detailed than items further down, because they are closer to being selected for a Sprint. Items that can be Done by the Scrum Team within one Sprint are considered ready for selection in Sprint Planning — they usually reach that degree of transparency after refinement. The Product Owner is accountable for the backlog's content and ordering, and for ensuring it is transparent, visible, and understood. Transparency here means everyone can see the backlog and understand what is in it and why it is ordered the way it is; a backlog that only the Product Owner understands is not transparent, however well organized it looks.

Refinement

Product Backlog refinement is the act of breaking Product Backlog items into smaller, more precise items. It is an ongoing activity, not an event — the Guide gives it no timebox and no prescribed meeting. Refinement adds details such as a description, order, and size, and the attributes vary with the domain of work. The Developers who will do the work are responsible for sizing, and the Product Owner may influence the Developers by helping them understand and select trade-offs. Refinement typically consumes a modest share of the Developers' time within a Sprint — the older Scrum Guide suggested up to 10% of capacity, but the 2020 Guide gives no percentage, so be careful: any exam option quoting a 10% refinement rule as current Scrum Guide content is wrong. What matters is that refinement happens continuously, so that the top of the backlog is always ready enough for the next Sprint Planning.

The Product Goal

The Product Goal is the commitment for the Product Backlog. It describes a future state of the product that serves as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog, and the rest of the backlog emerges to define what will fulfill it. A product is a vehicle to deliver value: it has a clear boundary, known stakeholders, and well-defined users or customers. A product could be a service, a physical product, or something more abstract. The Product Goal is the long-term objective for the Scrum Team, and the team must fulfill — or abandon — one objective before taking on the next. There is one Product Goal per product at a time. The Product Goal gives the backlog coherence: without it, the backlog is a wish list; with it, every item can be judged by whether it moves the product toward the goal.

The Product Goal also connects the backlog to the Sprint Goal. Each Sprint's goal is a step toward the Product Goal, and progress toward the Product Goal is discussed at every Sprint Review. The exam tests the commitment pairing — Product Backlog with Product Goal, Sprint Backlog with Sprint Goal, Increment with Definition of Done — because it is one of the most compact and testable structures in the Guide. If a question asks what the commitment for the Product Backlog is, the answer is always the Product Goal. If it asks how many Product Goals a product has, the answer is one at a time.

Worked scenario

A Product Owner manages a backlog of 200 items for a food delivery app. The top 20 items are small, well described, and estimated; the rest are vague ideas. The Product Goal is to make ordering dinner faster than cooking it. Each Sprint, the team selects from the top, and each Sprint the Product Owner refines the next items down the list, splitting large ideas and adding estimates with the Developers' help. When a stakeholder asks for a catering feature, the Product Owner weighs it against the goal — catering is a different market — and places it low in the backlog, explaining the reasoning. This is the Product Backlog working as designed: emergent, ordered, transparent, and governed by a single goal. The alternative — a backlog of 200 unprioritized items with no goal — is not a backlog at all, it is a pile.

What good backlog items look like

Items at the top of the Product Backlog share certain qualities: they are small enough to be Done within one Sprint, clear enough that the Developers understand what is needed, and valuable enough to justify the effort. They have a description that explains the need, an order that reflects their priority, and a size estimated by the Developers who will do the work. Items further down the backlog are larger and vaguer, and that is fine — they will be refined as they rise toward the top. The Product Owner's ongoing work is to keep the top of the backlog in this ready state, so that Sprint Planning can focus on selecting and planning rather than on clarifying. Transparency matters throughout: the backlog should be visible to everyone, and anyone should be able to understand what is in it and why it is ordered the way it is. A backlog that only the Product Owner can read is not transparent, however well organized it appears. When stakeholders ask why their item is not at the top, the Product Owner can point to the ordering and explain the value judgement behind it — that conversation is the backlog doing its job.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.Which statement BEST describes the Product Backlog?

Report an error

Q2.What is the commitment for the Product Backlog?

Report an error

Q3.What is Product Backlog refinement?

Report an error

Q4.How many Product Goals does a product have at one time?

Report an error

Q5.Which Product Backlog items are considered ready for selection in Sprint Planning?

Report an error

Q6.A manager keeps a separate list of urgent tasks and asks Developers to work from it alongside the Product Backlog. What is wrong with this?

Report an error

Q7.Which statement about the Product Goal is TRUE?

Report an error

Q8.During refinement, the Product Owner wants the Developers to size an item, but the Developers say they do not understand it well enough. What SHOULD happen?

Report an error

Q9.Which of the following is TRUE about the ordering of the Product Backlog?

Report an error