Product backlog examples use concise three-column models to clarify tasks, organize by priority, and use a unique numerical scoring system to figure out which tasks require the most effort. A product backlog tool can be incredibly effective for wading through built-up tasks and forging a clear path forward.

But who is responsible for prioritizing the product backlog? Likewise, who creates a product backlog item’s estimate? Ultimately, these decisions lie in the hands of the Product Owner. But due to the collaborative nature of group projects, you’ll want the entire development team’s input while you weigh your product backlog estimate.

You’ll determine whether or not a backlog item is considered complete based on the plan of action designed by your team.

As you establish your scrum product backlog example, you’ll need to come to a consensus on your Definition of Done (DoD). Some factors that might play into the DoD are if your product has passed accessibility tests or if it’s fully prepared to launch. The flexibility of a DoD, and of every product backlog sample, means that the definition of “complete” is entirely up to your team.

Each example of product backlog works to prioritize your items. Get started by downloading FigJam’s free customizable template and inviting the whole team to a shared meeting space. Together you can follow these simple steps to determine priorities and find your course of action.

1. Under columns labeled “Behind,” “On Track,” and “Complete,” add sticky notes to represent each corresponding task and a call to action.

2. Use a story point system to rate the effort behind each task. Look at a combination of time needed, challenge level, and due date to rate each task against one another.

3. Organize your sticky notes by difficulty, with the highest priorities at the top of your product backlog scrum example chart.