The product backlog is developed at the very beginning of a project. It is often developed in conjunction with the product vision. The product backlog keeps track of all the requirements along with their priority and the release they will be incorporated into.
The product backlog includes at least:
- Summary description
The product backlog is used to document and prioritize the requirements, features, functions, and user stories for releases or sprints. It is developed at the start of the project and is updated throughout the project.
Consider the following tips to help tailor the product backlog to meet your needs:
- You can add estimating information such as story points.
- To provide more detail you can indicate which sprint a feature or function will be incorporated into.
- You may want to indicate the user type that will benefit from the requirement, such as customer, administrator, manager, etc.
- For large projects it helps to categorize requirements, so having a column that indicates the category can be useful.
The backlog should be aligned and consistent with the following documents:
- Product vision
- Release plan
|ID||A unique identifier|
|Summary description||A brief description of the requirement or need. The description should be no more than one or two sentences.|
|Priority||A way of prioritizing or ranking the requirements. This can be in summary groups, such as high, medium and low, or it can be numbered 1, 2, 3.|
|Story||This field can either be a user story that is prioritized, or it can indicate the name of a user story that is recorded elsewhere.|
|Status||Indicates if the requirement is not started, in progress, or complete.|