What is the purpose of the portfolio backlog?

• A. It lists the program increments
• B. It stores risk registers
• C. It tracks Epic progress across the portfolio
• D. It holds the epics that made it thru Kanban, approved for implementation

Answer: (D)

The portfolio backlog is the holding area for Epics that have passed through the Portfolio Kanban and are approved to be implemented. Its purpose is to surface Epics that are ready for investment and funding decisions at the portfolio level, so leaders can prioritize, allocate resources, and plan how these large initiatives will be realized across Value Streams. This backlog feeds the next steps in the portfolio planning cycle and helps ensure work aligns with strategic themes and economic trade-offs.

It isn’t about listing program increments, storing risk registers, or tracking Epic progress across the portfolio. Those activities happen through other SAFe mechanisms: Program Increments are the timeboxes for implementation by Agile Release Trains, risk management lives in separate governance processes, and Epic progress is tracked through the Kanban and execution boards rather than the backlog itself.