HKSM
Retrospect Program or Portfolio Meeting
A retrospective held at the program or portfolio level that parallels a Retrospect Release Meeting, but occurs far less often due to its broader scope and strategic focus.
Key Points
- Focuses on cross-team, cross-product learning and improvement at the program or portfolio scale.
- Occurs less frequently than release retrospectives (often quarterly or at major milestones).
- Brings together program/portfolio leadership, key stakeholders, product management, and representatives from delivery teams.
- Produces high-level improvement actions, governance or policy adjustments, and roadmap or investment changes.
Example
After two quarters, a portfolio leadership group reviews outcomes from multiple release retrospectives, examines portfolio KPIs, and identifies systemic bottlenecks in dependency management. They decide to standardize integration practices, adjust funding between value streams, and create a portfolio-level improvement backlog to be tracked in the next planning increment.
PMP Example Question
Which statement best describes a Retrospect Program or Portfolio Meeting?
- A team-level ceremony held every sprint to inspect and adapt team practices.
- A program/portfolio-level retrospective, similar to a release retrospective, but convened less frequently to address systemic improvements.
- A detailed technical review conducted after each user story is completed.
- A status meeting used to report percent complete for all projects in the portfolio.
Correct Answer: B — A higher-level retrospective held less often to improve program or portfolio performance
Explanation: Unlike team or release retrospectives, this meeting examines cross-team, strategic issues and therefore happens less frequently.
