Product backlog templates are standardized repositories for tracking PBIs through prioritization and inclusion in sprints, usually retained in standard Excel format.
PBI items form a key part of any agile project plan. Template content includes high-level information that can readily be utilized by the product owner and Sprint leaders to accurately evaluate, monitor backlog items and sprint planning:
|Product Backlog Excel Template Free Download|
- Task name/description – This is a brief identifying description of the task to be performed by the backlog item.
- Story – This is a Y/N indicator to identify if there is a clear story behind the item, stating the item’s purpose and benefits.
- Dev Ready – Is the item ready for pulling into a sprint action? There are varying views of what “ready” means, but the values of Y/N tell the product owner that there is sufficient information for the PBI to be pulled forward into a sprint.
- Priority – the product owner establishes the priority of each PBI. This is based on a combination of business value, cost to implement (or cost savings), and story points. Values for priority are Low, Medium, and High.
- Status – Initially a story will be in a “Not Started” status. Once it has begun work as part of an active sprint, it will move to “In Progress” until such time that the task is delivered, making the status “Complete.”
- Story Points – Story points are unique to Agile estimating techniques, taking the place of traditional estimating in increments of hours or weeks. Story points are assigned as factors of difficulty for development either due to complexity or unknown factors required to complete the task. Scrum teams come to a consensus on the story points to be assigned to a PBI without a true relationship to estimates of hours. This value presents a realistic gauge of complexity as related to other tasks on the product backlog. Values for story points are generally set as numerical values such as 1,2,4,8,16, indicating the comparisons of very small through very large efforts required.
- Sprint – Once an item has been combined into a sprint exercise this entry tracks the sprint associated with the task. This column may include values of Y/N, or if sprint numbers are utilized may contain the actual sprint project designation.
- Release number and/or date – this can be utilized to record when the sprint results were actually implemented.
- Acceptance criteria – Where the product owner or designated stakeholders have specific requirements that must be met before acceptance, this column can be utilized to provide such details.
PBIs form a key part of all the sprint activities including but not limited to Sprint Review Meeting, Sprint Capacity Planning and Agile Reporting.