The Product Backlog

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of requirements for all work.

Key characteristics:

• Ordered: Not just prioritized—items are in a specific sequence
• Emergent: It evolves as the team learns
• Transparent: Anyone can see it
• Owned by the Product Owner: PO decides what's in it and the order

Items include:

• Features and enhancements
• Bug fixes
• Technical work
• Knowledge acquisition (spikes)

Product Backlog refinement is the ongoing activity of adding detail, estimates, and order to items. This happens continuously, not just in meetings.

What refinement produces:

• Smaller items that fit in a Sprint
• Clear acceptance criteria
• Enough understanding to discuss in Planning
• Estimates (if your team estimates)

How much time? The Scrum Guide suggests no more than 10% of Sprint capacity. For a 2-week Sprint, that's about 1 day total—often split into sessions.

Who does it? Product Owner and Developers collaborate. PO brings the "what and why"; Developers add "how" considerations and estimates.

Every artifact has a commitment. For the Product Backlog, it's the Product Goal.

The Product Goal describes a future state of the product. It serves as:

• A target the team plans against
• A filter for backlog items (does this serve the Goal?)
• Something to communicate to stakeholders

Product Goal characteristics:

• Larger than a single Sprint
• Concrete enough to measure progress
• The team pursues one Goal at a time

The entire Product Backlog serves the Product Goal. When the Goal is achieved (or abandoned), a new one is created.