Which backlog does the PgM manage?

• A. Team Backlog
• B. System Backlog
• C. PgM Backlog
• D. Release Backlog

Answer: (C)

Program-level backlog ownership is what this item tests. In SAFe, the Agile Release Train needs a backlog at the program level—the Program Backlog—that holds features and enablers cross-cutting multiple teams and guiding the train’s work across upcoming Program Increments. The Program Manager (PgM) is responsible for keeping this backlog well-groomed, prioritized by business value, and aligned with the program’s vision and roadmap. They work closely with Product Management, System Architecture, and the RTE, but the content, priority, and readiness of items in this backlog sit at the program level. Team backlogs belong to individual Agile Teams, while System Backlog covers system-level concerns and is typically managed by System/Architect roles; Release Backlog isn’t the dedicated backlog managed by the PgM. So, the backlog the PgM manages is the Program Backlog.