“Product Backlog Explained: What It Is & How to Create One” on Plaky, October 24, 2024
2. List all work items in the Backlog
Another tip? Always keep one Backlog only. Our collaborator, Alan Zucker, the Founding Principal of Project Management Essentials, explains why:
“The Backlog should be a single, prioritized list of all desired work. Multiple Backlogs occur when there is dysfunctionality. Different business areas or technologies cannot collaborate and develop a single list.”
4. Prioritize your work items in the Backlog
Another tip for prioritizing the Backlog is to list items in a ranked order. Alan Zucker explains why:
“A forced ranked ordering (1 to N) shifts the discussion about priorities and trade-offs early in the process and moves it from the development team to the business owners who should make these decisions.”
5. Refine the Backlog
According to Alan Zucker, larger Backlog items should always be broken down into smaller ones:
“By definition, items at the top of the Backlog should be small enough to be completed within the iteration/Sprint. Most Agile coaches recommend making them even smaller. I recommend that items at the top of the Backlog be completed within a few days.”