HKSM

The program-level product backlog after it has been routinely refined to reflect changes, new requirements, and the latest learning across teams.

Key Points

• It is a living, program-wide backlog that is frequently reviewed and adjusted.
• Refinement may add, remove, split, or reprioritize features and enablers.
• Updates are driven by stakeholder feedback, market shifts, dependencies, risks, and compliance needs.
• Maintained through ongoing backlog refinement events that align multiple teams on priorities.

Example

After a customer demo and a new regulatory notice, the program team revisits its backlog. They add new compliance epics, split a large feature into smaller ones, and move a security item higher in priority. The result is the updated program product backlog that guides the next Program Increment.

PMP Example Question

During quarterly planning, several teams report new dependencies and a regulatory change that affects scope. Which artifact should be revised to capture these changes and reprioritize program-level work?

1. Program Increment Objectives
2. Updated Program Product Backlog
3. Team Kanban Board
4. Definition of Done

Correct Answer: B — the regularly refined program backlog that incorporates new requirements and changes.

Explanation: The Updated Program Product Backlog is the program-level backlog after refinement, reflecting new information, dependencies, and priority adjustments.