Prioritized Program or Portfolio Backlog Review Meetings
At the program or portfolio tier, each project in the program or each program in the portfolio sends a delegate. To keep the session efficient, limit attendance to a single representative from each project or program.
Key Points
- Conducted at the program or portfolio level to review and rank backlog items across projects or programs.
- Attendance is streamlined: one representative per project or program to enable fast decision-making.
- Decisions consider strategic alignment, value, dependencies, risks, and capacity constraints.
- Outputs include an updated prioritized backlog, sequencing decisions, and actions to manage cross-team dependencies.
Example
A portfolio has three programs delivering digital products. For the monthly backlog review, each program sends one representative. Together with the portfolio lead, they assess proposed epics, resolve sequencing conflicts, and produce a single prioritized portfolio backlog for the next quarter.
PMP Example Question
To streamline a portfolio backlog review, which attendee list best fits good practice?
- All Scrum Masters from each delivery team
- One representative from each program plus key portfolio stakeholders
- Every project manager and product owner across the organization
- Only the portfolio manager
Correct Answer: B — One representative from each program with necessary stakeholders
Explanation: These meetings operate at the program or portfolio level and are kept efficient by limiting attendance to a single delegate from each project or program while involving essential decision-makers.
HKSM