Maintaining the backlog
The product backlog is an ordered list of project-specific work items, small or large, that are candidates for implementation. Using Scrum terminology, these items are referred to as user stories. Pega Express™ uses the term epics to denote groupings of user stories.
The user stories and epics cover a wide variety of types of work, such as:
- Ideas for new features or enhancements
- Application issues that require attention
- Work required to address technical updates
Backlog creation
You can use the stories automatically created and imported into Agile Workbench by Pega GenAI Blueprint™ as a starting point for your project backlog. It already contains documentation for many of the features and sub-features that become user stories and epics.
The key to creating your backlog is to understand that it can change over time. There is no expectation for 100% detail in the first draft. Your team refines the backlog as the team gathers more information and elaborates user stories over time. Your team gathers inputs from the Product Owner, Business Analysts (BA)s, Lead System Architect (LSA), and testers. Creating your backlog requires a diverse range of viewpoints to understand what is important, what to prioritize, and when to deliver each user story.
Backlog prioritization
Backlogs are continually evolving and changing over time. While the Product Owner is responsible for prioritizing the backlog, you, as the Pega Business Architect, meet regularly with the PO to update and advise them on the current status of the project.
Along with the PO, you ensure the backlog includes up-to-date user stories and is prioritized in line with the business value the user stories deliver. New user stories may be prioritized over others, and some may be replaced. Existing user stories may no longer be needed and may be removed. Backlog management and prioritization is an ongoing activity that continues through all phases of the project.
Backlog creation and maintenance
The Product Owner owns the backlog. The PO creates the backlog, keeps it up to date, and prioritizes the user stories. At the start of the project, the Product Owner and the project team must agree on the management approach for the project and application's work items.
When making prioritization decisions, the Product Owner has a wide range of user stories. Some stories are elaborated and are well understood and ready for Build. Others are still in the early stages of the user story life cycle. This variety means that the Product Owner must consider both short term goals for the sprint planning and longer-term goals for elaboration planning as they prioritize stories in the backlog.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?