What is a Backlog?
A backlog is a prioritised list of work that is derived from requirements and the roadmap. The most important items of highest value will be at the top where the feature team can pull items according to their capacity.
Programme Backlog
- Contains all requirements from Country and Centre Business.
- The programme backlog is owned by the Prioritisation committee and they are responsible for prioritising the requirements before filtering it down to the individual teams’ product backlog.
Product Backlog
- The Product Owner from each team will take the highest priority items from the programme backlog and write them as epics.
- Product backlog grooming takes place on a weekly basis were the stories are broken up according to the INVEST principles and sized.
- The Product Owner team will prioritised the stories to ensure that the teams take on the highest priority items.
Iteration Backlog
The feature team will pull the top priority stories from the product backlog within the story points the team can take on.
Things to look out for (anti-patterns)
- Product Owners dictate the priority of work items in the backlog, while the feature team dictates the velocity through the backlog.
- The Product Owner prioritises the backlog at the start of the project, and doesn’t frequently re-look at the priorities based on feedback received from users, stakeholders and development team.
- The feature team limits items on the backlog or only take on stories that are customer facing.
- The backlog is kept as a document and interested parties don’t have access or different versions are used.
BA Agile Framework 