Feature requests, bug reports, and new ideas pile up fast. A product backlog gives them one ordered home, so your team always knows what to build next and can walk into sprint planning with clear priorities.
What is a product backlog and why is it important?
A product backlog outlines all the requirements for a software development project in priority order. Anytime new work comes up during product development, it’s added to the backlog, often as a user story. That way, nothing gets lost.
Product development keeps changing, and a Scrum backlog should change with it, so your team always works from current priorities.
The product owner is accountable for ordering the product backlog. The developers who’ll do the work size each item, because they know what it takes to build. Every backlog also serves one product goal, the longer-term objective each item should move the product toward.
On Agile teams, the order matters as much as the contents. Once the top items are ordered and sized, they become dated sprint work on a Gantt chart that stakeholders can read at a glance.
Tips for prioritizing the product backlog
Here’s how to ensure your product backlog sets you up for successful sprint planning:
Mark your top-priority items, and schedule them to start in your next sprint.
Don’t include every possible task related to your project in the backlog. This takes the focus away from higher priority tasks. Every item listed in the backlog should add value to the product.
Re-evaluate your backlog frequently. Check that every user story is still important and relevant. Mark items as complete when the work’s been shipped.
Assign story points to indicate the level of effort, rather than estimated time, required to build a product feature or resolve a bug.
Backlog items can be very granular, but they don’t have to be. Tasks are usually broken down more thoroughly during the sprint planning process.
Order items by the goal of your next sprint first, then by value and risk. Before you finalize the top of the list, check what each item needs to start. A high-value story that depends on unfinished prerequisites will stall the sprint, so move those prerequisites up with it.
Product backlog vs. sprint backlog
A product backlog holds all the work planned for a product, while a sprint backlog holds only the work selected for the current sprint. The 2020 Scrum Guide calls the product backlog “an emergent, ordered list of what is needed to improve the product.” The sprint backlog combines the sprint goal, the items picked for the sprint, and the developers’ plan for delivering them.
Here’s how the two compare:
Product backlog | Sprint backlog | |
Who owns it | The product owner, who is accountable for ordering it | The developers, since it’s their plan for the sprint |
Time horizon | The life of the product | One sprint |
How it changes | Items get added, refined, reordered, or removed at any time | Developers update it throughout the sprint as they learn more |
Commitment | Product goal | Sprint goal |
The sprint backlog is more flexible than many teams assume. Developers can negotiate scope with the product owner mid-sprint, as long as the sprint goal stays intact. Work that doesn’t meet the team’s definition of done goes back to the product backlog.
In TeamGantt, the product backlog can live as its own project. Each sprint then becomes a dated group of tasks you pull onto a board.
How to create a product backlog
Building a product backlog comes down to two things: knowing what goes in it, and putting those items in the right order.
What goes in a product backlog
User stories: A simplified requirement written in the end user’s voice, usually in this format: As a [type of user], I want [goal] so that [reason]. New ideas get framed as user stories before they’re added to the backlog.
Features: New or improved functionality that gives users value. Each feature should trace back to a user story.
Tasks: Smaller pieces of work that break a complex feature into buildable steps. Some teams track tasks in the backlog, and others add them during sprint planning.
Enhancements: A proposed improvement to an existing feature, so it delivers more value to users.
Bugs: Defects found during product use. Keeping track of bugs in the backlog makes it easier to prioritize and plan fixes with each new sprint cycle.
5 steps to build your product backlog
Start with a product goal, then fill, order, and size the list:
Write a one-sentence product goal, and connect it to your product roadmap so each item traces back to a planned outcome.
Capture every request, idea, and known bug as a backlog item, using the user story format for anything a user will touch.
Move the items that serve your next sprint to the top, and leave everything else in rough order below.
Ask the developers who’ll do the work to size the top items in story points.
Schedule a recurring refinement session so the next few items are ready before each sprint planning meeting.
Product backlog example
Here’s a product backlog for a four-person team building an appointment-booking app for a veterinary clinic. The first release already lets pet owners book visits online. The goal for the next sprint is to let clients manage their own appointments without calling the front desk.
Order | Item | Type | Story points |
1 | Booking confirmations show the wrong time for clinics in the Central time zone | Bug | 2 |
2 | As a pet owner, I want to reschedule my appointment online so that I don’t have to call the clinic. | User story | 5 |
3 | As a pet owner, I want to cancel an appointment online so that the slot opens up for someone else. | User story | 3 |
4 | Appointment reminder texts with a link to reschedule | Feature | 8 |
5 | As a vet, I want to block off surgery time so that clients can’t book over it. | User story | 3 |
6 | Show the pet’s name and visit reason on the front desk’s daily schedule | Enhancement | 2 |
7 | As a pet owner, I want to upload vaccination records so that the clinic has them before the visit. | User story | 13 |
The time zone bug sits at the top because it affects every live booking and takes little effort to fix. Rescheduling and canceling come next since they serve the sprint goal directly, and the reminder texts depend on the reschedule link existing first. The vaccination upload stays at the bottom until refinement breaks it into smaller stories the team can size with more confidence.
How to refine your product backlog
Product backlog refinement is the ongoing work of breaking items into smaller, more precise pieces and adding the detail needed to order and size them. Some teams still call it backlog grooming. Refinement can happen anytime, but a dedicated session keeps the top of the backlog ready for sprint planning.
Use this agenda for a refinement session:
Review the product goal and the likely goal for the next sprint.
Walk through the top items in order, and confirm each one still serves that goal.
Split any item that’s too large to finish in one sprint.
Add acceptance criteria, and attach the designs or notes developers need.
Have the developers size each item, then let the product owner settle the final order.
How to manage your product backlog in TeamGantt
In TeamGantt, your product backlog works across three views, so each part of the process has a natural home:
Schedule sprints in Gantt view. Drag tasks into an upcoming sprint, or move entire groups of tasks to reschedule a sprint. Add dependencies for items that have to happen in order, and use task colors to mark priority, sprint, or readiness.
Refine in List view. Drag items into a new order during refinement sessions, and add story points, acceptance criteria, and wireframes in each task’s Edit window.
Run sprints in Board view. Create a board for each sprint, with columns that match your process, like in development, QA, and done. You can set columns to move tasks automatically when they hit a certain percent complete, and highlight stale cards that haven’t moved in a set number of days.
Keep the board and timeline in sync. Cards stay in sync with your Gantt chart, so progress, dates, and comments match in both places.
Pull from several backlogs at once. A custom board uses an Inbox with saved filters, so new tasks that match land ready to drag into a sprint column. You can also open multiple projects in one Gantt chart to manage resources across them.
Discuss work on the task. Use comments to share updates and attach requirements documents.
Product backlog template
Our product backlog template sets up a ready-made backlog project in TeamGantt that you can adapt to your own product.
To make it yours, replace the sample items with your own backlog and rename the groups to match your sprints. Add dates to the top items once they’re sized and ready to schedule.