This post is a slightly updated version of the one published earlier
- Product backlog always lists items adding value for the customer. It includes functional requirements and non-functional requirements. It can also include items required by the team, but only the ones that will eventually bring value to the customer, e.g. taking into use a continuous integration server in order to guarantee the continuous end product quality.
- Product backlog cannot include concrete low level tasks and requests for building the intermediate artifacts. For example, it cannot include request for producing the design document unless customer has to ship it further for some purpose.
- Product backlog utilizes the simplest and the most effective way for prioritizing requests - a simple list. Such a method does not allow for having 100 absolute max priority features and forces the product owner to actually make decisions about the feature priorities.
- The higher the items are located on the product backlog, the more detailed they are. Items for the closest couple of months are usually quite detailed, while items that will be worked on in some 6-12 month can be defined very broadly and imprecisely.
- When there are several interdependent teams in the company or department, typically they all have a single product backlog and pull their work from it.
- Product backlog does not typically include the detailed requirement information. Usually the final requirement details are figured out with the help of the customer, when the requirement is being implemented.
Ease of use, clear and transparent purpose is what makes the product backlog so useful for seeing into the project status.
Do you agree with the properties above? Or are there any other important product backlog properties worth mentioning?