What are program epics?

• A. They are small stories in a sprint
• B. They are used only in the portfolio backlog
• C. Carry large initiatives into program backlog and split portfolio epics for implementation
• D. They are QA test suites

Answer: (C)

Program epics represent large initiatives that require coordination across multiple teams and often across an ART, spanning more than a single PI. They’re created to translate portfolio-level work into something that a program can implement, so they live in the program backlog and are broken down into smaller, actionable program-level work (program epics) that fit into PIs and can be delivered by the teams.

This is why the option describing carrying large initiatives into the program backlog and splitting portfolio epics for implementation is the best fit: portfolio epics are too big to implement as-is, so they are decomposed into program epics that can be planned, coordinated, and delivered within a program, across the teams involved.

Small stories in a sprint aren’t epics, and QA test suites aren’t epics either. Epics sit above the team backlog and above individual user stories, serving as the bridge from strategic portfolio work to concrete program-level delivery.