25 Questions — PMI – PgMP : Certified Program Management Professional - Domain 5 - Program Governance

Expand any question to reveal the correct answer and explanation.

1. 1 A program steering committee is struggling to reach a consensus on a high-impact change request that affects three of the five component projects. As the program manager, how should you facilitate the governance process to ensure strategic alignment?

   Consider the primary metric used to measure success at the program level versus the project level.

   Evaluate the change's impact on the benefits realization plan and present a quantified trade-off analysis to the committee.

   Governance decisions at the program level must be predicated on protecting and realizing the strategic benefits that justify the program's investment.

   • ✗ Recommend the change be approved if the majority of project managers agree the technical scope is feasible.

     Project-level feasibility is a tactical concern that does not address whether the change erodes the program's overall business case or strategic value.

   • ✗ Delegate the final decision to the project manager of the most expensive component project to ensure budget compliance.

     Assigning decision rights based solely on budget size ignores the interdependencies and strategic priorities that governance boards are designed to adjudicate.

   • ✗ Implement the change immediately to maintain stakeholder satisfaction, then update the program roadmap during the next quarterly review.

     Bypassing integrated change control undermines the governance framework and risks cascading failures across interdependent program components.

2. 2 During a phase-gate review, it is discovered that a component project's deliverables no longer align with the updated organizational strategy. What is the most appropriate governance action for the program manager to recommend?

   Think about the role of the governance board in investment prioritization and resource optimization.

   Terminate or re-scope the component to redirect resources toward initiatives that support the new strategic drivers.

   Governance structures must be adaptive, allowing for the cessation of work that no longer contributes to the program’s intended business outcomes.

   • ✗ Continue the project until the next milestone to avoid wasting the resources already consumed.

     The sunk cost fallacy should not override the governance requirement to terminate or re-baseline initiatives that no longer provide strategic value.

   • ✗ Fast-track the remaining project tasks to deliver the outputs before the strategy shifts further.

     Accelerating a misaligned project only delivers irrelevant outputs faster, failing the core principle of benefits realization.

   • ✗ Ask the project manager to modify the project charter independently to match the new strategy.

     Independent charter modifications bypass program-level oversight and can create conflicts with other interdependent components.

3. 3 Which of the following best describes the integration of the 'Collaboration' performance domain introduced in the Fifth Edition of the Standard for Program Management into the governance framework?

   Look for the concept that treats the program as more than just a collection of isolated projects.

   It emphasizes managing the program as a whole system, leveraging collective human capabilities across component teams.

   The collaboration domain supports other domains by focusing on team integration and cooperative leadership to optimize the program as a unified system.

   • ✗ It serves as a rigid set of compliance rules to be enforced by the Program Management Office.

     The standard emphasizes adaptive frameworks over rigid barriers to support continuous improvement and team integration.

   • ✗ It replaces the need for a formal governance board by allowing teams to self-govern through consensus.

     While collaboration is essential, formal governance remains the backbone for decision-making, oversight, and accountability.

   • ✗ It restricts the program manager's authority to make decisions without unanimous stakeholder approval.

     Collaboration aims for alignment and synergy, not necessarily unanimous consent, which can paralyze executive decision-making.

4. 4 A program manager is calculating the potential net benefits ($NB$) of a program. If the realized benefits from component $i$ are $B_{realized, i}$, the delivery costs are $C_{delivery, i}$, and operational maintenance is $C_{sustainment}$, which formula represents the program's value to the organization?

   Consider how you would determine the total profit or value by accounting for every expense associated with delivery and long-term upkeep.

   $NB = \sum_{i=1}^{n} (B_{\text{realized}, i} - C_{\text{delivery}, i}) - C_{\text{sustainment}}$

   Net benefits are derived by subtracting both the execution costs of all components and the long-term operational costs from the total realized benefits.

   • ✗ $NB = \sum_{i=1}^{n} (B_{\text{realized}, i} + C_{\text{delivery}, i}) + C_{\text{sustainment}}$

     This formula incorrectly adds costs to benefits, resulting in an inflated and inaccurate value metric.

   • ✗ $NB = \frac{\sum B_{\text{realized}, i}}{\sum C_{\text{delivery}, i}} \times 100$

     This represents a benefit-cost ratio percentage rather than the absolute net benefit value required for strategic financial governance.

   • ✗ $NB = \sum_{i=1}^{n} (B_{\text{realized}, i}) - (C_{\text{delivery}, i} \times C_{\text{sustainment}})$

     Multiplying delivery costs by sustainment costs is mathematically irrelevant to determining the net value of program outcomes.

5. 5 When establishing a program governance board, what is the primary reason for defining specific 'escalation paths' and 'decision timeboxes'?

   Think about the consequences of having 'unowned' or 'floating' risks and issues in a complex program environment.

   To prevent program-level issues from remaining unresolved and delaying the realization of strategic benefits.

   Clear escalation protocols and time-bound decision-making minimize the risk of 'floating' issues that can disrupt cross-component dependencies.

   • ✗ To ensure that project managers do not have to make any difficult decisions themselves.

     Escalation paths are for issues exceeding project-level authority, not for abdicating standard project management responsibilities.

   • ✗ To satisfy the administrative reporting requirements of the senior executive team.

     While reporting is a function of governance, the primary purpose of these structures is active control and benefit protection, not just administration.

   • ✗ To allow the program manager to focus exclusively on technical delivery instead of stakeholder management.

     Governance actually increases the program manager's involvement in stakeholder orchestration and executive-level coordination.

6. 6 In the context of program governance, how should a program manager handle a request from a high-power stakeholder for a scope expansion that does not align with the program charter?

   Consider the governance action required when benefit forecasts or strategic priorities materially change.

   Perform a rigorous impact assessment and require a re-justification of the business case through the governance board.

   Changes that materially alter the program's intent must be validated against the organizational strategy through formal governance channels.

   • ✗ Approve the request immediately if the stakeholder provides the additional funding required.

     Funding alone does not justify scope expansion if it deviates from the strategic mission and benefits defined in the program charter.

   • ✗ Reject the request outright to maintain the original baseline and avoid scope creep.

     Categorical rejection without analysis ignores the possibility that the organization's strategic priorities may have shifted, necessitating a program change.

   • ✗ Incorporate the change into a single project’s scope statement to avoid complicating the overall program roadmap.

     Hiding program-level changes within individual projects obscures the true impact on interdependencies and governance oversight.

7. 7 Program Governance Tasks in the ECO include 'Obtaining authorization(s) and approval(s) through stage gate reviews.' What is the critical distinction between a 'milestone' and a 'stage gate'?

   Focus on which concept implies an active 'approval to proceed' versus a simple marker of 'work finished'.

   A milestone represents a technical completion, whereas a stage gate is a formal go/no-go decision based on continued business justification.

   Stage gates are governance control points used to validate if the program still aligns with the business case and should proceed to the next phase.

   • ✗ Milestones are defined by the program manager, while stage gates are only defined by the individual project managers.

     Stage gates are program-level governance events, typically involving senior sponsors and steering committees, rather than just project managers.

   • ✗ A milestone is used to measure cost, while a stage gate is used solely to measure schedule performance.

     Both milestones and stage gates can relate to various performance metrics, but their primary distinction lies in their decision-making authority.

   • ✗ There is no functional distinction; the terms are used interchangeably in the Standard for Program Management.

     The standard and the ECO clearly differentiate between markers of progress and formal decision-making points for phase transition.

8. 8 A program manager identifies a risk that could impact the data security of four different projects within the program. According to Domain 5 (Governance), what is the most appropriate repository for this information?

   Consider the level of visibility needed for a threat that crosses project boundaries.

   A centralized program-level risk register managed through the Program Management Office (PMO).

   Program governance necessitates aggregating risks that emerge from project interactions or span multiple components into a single holistic view.

   • ✗ The risk register of the project that first identified the issue.

     Local project registers are insufficient for managing cross-cutting risks that require program-level visibility and resources.

   • ✗ A private log maintained by the program manager to avoid causing concern among project teams.

     Transparency and formal documentation in a PMIS are required for accountable governance and effective stakeholder communication.

   • ✗ The organizational lessons learned repository, to be reviewed after program closure.

     Active risks must be managed during execution; deferring action to the lessons learned phase fails to protect the program's benefits.

9. 9 Which guiding principle from the Fifth Edition Standard is most directly supported by the establishment of a formal Program Steering Committee with named decision rights?

   Think about which principle specifically addresses decision-making structures and organizational accountability.

   Governance

   The principle of Governance involves setting up structured decision-making, oversight, and escalation paths to ensure organizational accountability.

   • ✗ Synergy

     Synergy focuses on coordinating components for collective value, which is a result of good governance but not the principle of governance itself.

   • ✗ Team of Teams

     The Team of Teams principle centers on collaborative leadership and coordination between project teams, rather than executive oversight.

   • ✗ Benefits Realization

     Benefits realization is the target outcome, while governance provides the framework and decision rights required to achieve that outcome.

10. 10 A program manager is tailoring the governance framework for a transformation program that includes both Agile and Predictive (Waterfall) components. What is the most effective governance strategy?

    Look for the approach that balances flexibility at the component level with control at the program level.

    Establish an integrated governance model that accommodates both approaches while aligning their outcomes to shared benefit milestones.

    Effective program governance provides a unified framework that respects local delivery styles but ensures all components remain strategically aligned.

    • ✗ Mandate that the Agile components adopt Waterfall reporting structures to ensure uniformity.

      Forcing artificial uniformity often destroys the specific value and efficiency that different delivery methodologies provide.

    • ✗ Manage only the Waterfall projects and allow the Agile teams to self-organize without program-level oversight.

      Exempting Agile teams from program governance creates silos and obscures the visibility of interdependencies and benefits realization.

    • ✗ Use the most recently developed methodology for all projects to simplify the governance audit trail.

      Methodology selection should be based on the project's specific needs, not the administrative convenience of the governance audit.

11. 11 According to the PgMP ECO, the task of 'Establishing escalation policies and procedures' is intended to ensure that:

    Think about the role of 'thresholds' in managing complexity and executive visibility.

    Risks and issues are handled at the appropriate level of authority based on predefined thresholds.

    Escalation procedures define when an issue exceeds the current management level's authority, ensuring timely and appropriate resolution.

    • ✗ All project-level risks are handled by the senior organizational executives.

      Over-escalation burdens executives with tactical issues that should be resolved at the project or program level.

    • ✗ The program manager is personally responsible for all financial overruns across the program.

      Escalation is a process for decision-making, not a mechanism for assigning personal blame for program complexities.

    • ✗ No project manager can make a decision without the program manager's written approval.

      Governance should empower project managers within their defined scope; micro-management is not equivalent to effective governance.

12. 12 The Fifth Edition Standard reclassified Integration Management. In the current governance framework, how is Integration Management positioned?

    Look for the answer that reflects integration as an 'ongoing' and 'connective' process.

    As a continuous program activity that connects all performance domains and program components.

    The updated standard positions Integration Management as an ongoing responsibility that links domains and components throughout the program lifecycle.

    • ✗ As a one-time activity occurring only during the program formulation phase.

      Integration is no longer seen as a discrete phase but as an ongoing responsibility across the entire lifecycle.

    • ✗ As a sub-task strictly confined within the Program Life Cycle Management domain.

      Previous editions grouped integration strictly inside the Lifecycle domain, but the current standard recognizes its broader, cross-domain role.

    • ✗ As a responsibility reserved exclusively for the Program Governance Board.

      Integration is a core competency of the Program Manager, supported by the governance framework but executed as a management activity.

13. 13 A program manager is designing a 'Program Management Information System' (PMIS) as part of the governance framework. What is the primary governance-related benefit of a centralized PMIS?

    Focus on the concepts of 'transparency' and 'decision support'.

    To ensure transparency and consistent reporting of program status and benefits realization to stakeholders.

    A centralized PMIS provides a 'single source of truth' for the data needed to make informed governance decisions and align stakeholders.

    • ✗ To automate the creation of project schedules without human intervention.

      A PMIS supports data management but does not replace the strategic expertise required for schedule development.

    • ✗ To allow stakeholders to change project requirements directly without a change control process.

      Ungoverned access to requirements would destroy the program's strategic alignment and baseline control.

    • ✗ To reduce the program manager's need for direct communication with the project teams.

      Information systems augment communication but cannot replace the leadership and relationship management required of a program manager.

14. 14 In Domain 5 (Governance), which document is typically used to specify roles, responsibilities, and decision authorities between the program and project levels?

    Look for an artifact that addresses 'who' has 'what' level of authority.

    Accountability Matrix (e.g., RACI)

    An accountability matrix clearly differentiates roles and responsibilities, which is essential for establishing governance decision rights.

    • ✗ Work Breakdown Structure (WBS)

      A WBS decomposes work into deliverables but does not define the authority levels or governance roles of the personnel involved.

    • ✗ Project Scope Statement

      A project scope statement focuses on the technical delivery of a single component rather than program-wide governance structures.

    • ✗ Program Risk Register

      While it documents risks, it is not the primary artifact for defining general decision-making authority and governance roles.

15. 15 A program manager is evaluating 'environmental scanning' as a governance task. How does this task support program success?

    Think about the 'external context' and 'strategic alignment' rather than physical or ecological environments.

    By continuously monitoring the external and internal business context to identify changes that may affect strategic alignment.

    Governance requires scanning for shifts in the market, technology, or corporate strategy that could necessitate a re-baseline of the program.

    • ✗ By ensuring the program team complies with local environmental and ecological regulations.

      While regulatory compliance is important, 'environmental scanning' in program management refers to the broader business and strategic context.

    • ✗ By performing daily health checks of the project team's office environment and morale.

      Morale tracking is a leadership function, whereas environmental scanning is focused on strategic and programmatic relevance.

    • ✗ By scanning project deliverables for technical defects before they reach the quality audit phase.

      This describes a quality control activity at the project level, not a strategic governance task.

16. 16 A Program Steering Committee quorum cannot be met for a critical phase-gate review due to an urgent corporate merger. What is the most appropriate action for the program manager?

    Look for the established procedure used when normal governance channels are blocked.

    Document the situation and invoke the agreed-upon governance escalation path to obtain temporary decision authority or a rescheduled review.

    Governance frameworks include escalation protocols specifically for situations where the standard decision-making process is disrupted.

    • ✗ Approve the phase transition yourself to keep the program on schedule.

      Program managers do not have the authority to bypass phase-gate approvals, as this violates core governance accountability.

    • ✗ Proceed with execution but tell the project managers to ignore any risks until the committee can meet.

      Proceeding without authorization and ignoring risks is a failure of both governance and risk management.

    • ✗ Cancel the program immediately, as the lack of a committee meeting indicates a total loss of sponsor support.

      A temporary scheduling conflict does not equate to the withdrawal of strategic support; termination requires a formal business case review.

17. 17 According to the Standard for Program Management, what is the role of the 'Program Business Case' in the governance process throughout the program lifecycle?

    Focus on the concept of 'continued viability' and 'justification for investment'.

    It serves as the primary reference for validating continued program viability during stage-gate reviews.

    Governance authorities use the business case to determine if the program's expected benefits still justify the ongoing expenditure.

    • ✗ It is a static document that is archived once the program is authorized.

      The business case must be dynamic, serving as a baseline for continuous evaluation during governance reviews.

    • ✗ It is used only to track individual project expenses at a tactical level.

      Tracking tactical expenses is a function of the program budget; the business case evaluates the overall value proposition.

    • ✗ It is a marketing document used solely to secure initial funding from external investors.

      While it helps secure funding, its internal role is to provide the strategic justification for every stage of the program's execution.

18. 18 During a governance audit, it is found that project-level change requests are being approved without assessing their impact on program-level interdependencies. This is a failure of:

    Think about the specific governance mechanism that manages 'impact across components'.

    Integrated Change Control under Program Governance

    Governance ensures that changes at the project level are reviewed for their systemic impact on the program's overall roadmap and benefits.

    • ✗ Strategic Program Alignment

      While alignment is affected, this is primarily a procedural failure of the established control and oversight mechanisms.

    • ✗ Stakeholder Engagement

      Stakeholders may be involved, but the failure to evaluate cross-project dependencies is a breakdown in the governance structure.

    • ✗ Program Life Cycle Management

      Lifecycle management executes the change, but governance provides the authority and framework for the change decision.

19. 19 Which of the following describes the relationship between 'Program Risk Management' and 'Program Governance' according to the Fifth Edition Standard?

    Consider how high-level risks are brought to the attention of executive sponsors.

    Governance provides the oversight and escalation paths required to address risks that exceed the program manager's authority.

    Risk management and governance are integrated; the governance board approves risk response strategies and handles high-level escalations.

    • ✗ They are unrelated functions with completely separate reporting structures.

      Risk management is a critical input for governance decision-making and oversight.

    • ✗ Governance is a subset of risk management used only when a program is in distress.

      Governance is a continuous performance domain used throughout the program, not just during crisis management.

    • ✗ Risk management replaces governance once the program enters the benefits delivery phase.

      Both functions operate concurrently throughout the entire program lifecycle.

20. 20 The 'Program Roadmap' is a key governance artifact. What is its primary function in a governance review?

    Think about 'sequencing', 'milestones', and 'benefit realization' over time.

    To provide a high-level visualization of component sequencing, major milestones, and the chronologic realization of benefits.

    The roadmap helps governance boards understand the timing of value delivery and the dependencies between major program components.

    • ✗ To show the detailed daily work schedule of every team member.

      Detailed daily schedules are project-level artifacts (Project Schedule); a roadmap is a high-level strategic visualization.

    • ✗ To serve as the legal contract between the program manager and the external vendors.

      Contracts are legal procurement documents; the roadmap is a strategic management and communication tool.

    • ✗ To replace the program charter as the formal authorization document.

      The charter provides authorization; the roadmap provides the plan for executing that authorized strategy.

21. 21 A Program Management Office (PMO) is often established to support program governance. Which of the following is a primary governance responsibility of the PMO?

    Look for concepts related to 'standardization', 'policy', and 'oversight'.

    Defining and enforcing program management standards, policies, and cross-project reporting structures.

    The PMO provides the structural support and standardization necessary for consistent governance and oversight across all program activities.

    • ✗ Hiring and firing individual project team members.

      Direct personnel management is typically handled by project managers or functional managers, not the PMO governance function.

    • ✗ Writing the technical code for all software projects within the program.

      The PMO is a management and governance body, not a technical execution unit.

    • ✗ Serving as the sole decision-maker for all program-level change requests.

      Decision rights for major changes usually rest with a Steering Committee or Governance Board, while the PMO facilitates the process.

22. 22 In the PgMP application process, which area of the Program Management Experience Summaries specifically evaluates your ability to handle complex decision-making and escalation?

    Think about which of the three essay domains focuses on 'frameworks' and 'structured oversight'.

    Program Governance

    The Governance summary requires candidates to describe how they established oversight, handled escalations, and used decision-making frameworks.

    • ✗ Program Strategy Alignment

      Strategy alignment focuses on the 'why' and the roadmap, rather than the internal mechanics of decision-making.

    • ✗ Program Leadership

      Leadership focuses on stakeholder orchestration and conflict resolution between people, rather than structural frameworks.

    • ✗ Project Delivery Management

      Project-level delivery is a tactical concern and is not one of the three core domains tested in the PgMP experience summaries.

23. 23 Which task from Domain 5 (Governance) involves 'Establishing processes and procedures for maintaining proactive program management oversight'?

    Focus on the 'model structure' and 'conformance to organization requirements'.

    Selecting a governance model structure that conforms to organizational requirements.

    The core of proactive oversight is choosing and implementing a governance model that matches the organization's standards and needs.

    • ✗ Directly managing the daily activities of the project team.

      Direct management is a project-level activity, whereas governance is about high-level oversight and decision frameworks.

    • ✗ Manually approving every project-level risk response plan.

      Effective governance uses thresholds to ensure only high-level or cross-cutting risks are reviewed by the program level.

    • ✗ Creating a new software application to automate all project management tasks.

      Governance is about processes and authority, not the creation of specific technical tools unrelated to management.

24. 24 A program manager is accused of bypassings governance because they reallocated resources between two projects without board approval. If the governance model specified that the program manager has a $\$50,000$ discretionary budget for resource optimization, and the move cost $\$30,000$, what is the correct evaluation?

    Consider the role of 'authority levels' and 'thresholds' in governance.

    The program manager acted within their defined authority levels as specified in the governance model.

    The program manager is empowered to make decisions within their established discretionary limits, which is a key part of an adaptive governance framework.

    • ✗ The program manager failed to follow governance because any resource shift requires a steering committee vote.

      Effective governance frameworks define thresholds (discretionary authority) to allow the program manager to optimize without constant board intervention.

    • ✗ The program manager should have asked the project managers for permission first, regardless of the budget.

      Governance authority flows from the charter and the steering committee to the program manager, not from the project level up.

    • ✗ The action was a violation of the 'Synergy' principle because it favored one project over another.

      Synergy involves optimizing the program as a whole, which often requires moving resources to high-value initiatives to benefit the entire program.

25. 25 According to the Fifth Edition Standard, why should program governance be 'adaptive' rather than 'rigid'?

    Think about how a program survives in a world where organizational strategies can change overnight.

    To ensure the governance framework remains relevant and effective as the program complexity and organizational environment shift.

    Rigid governance can become a barrier to success in high-ambiguity environments; adaptation ensures oversight remains supportive of the program's strategic goals.

    • ✗ To allow the program manager to ignore the rules whenever they feel it is necessary.

      Adaptive governance still follows a framework but can be tailored to meet changing program needs and complexities.

    • ✗ Because rigid governance is only required for small, simple projects.

      Small projects often have simpler governance, but large programs require sophisticated and flexible frameworks to manage high complexity.

    • ✗ To reduce the cost of maintaining the Program Management Office.

      The primary driver for adaptive governance is strategic effectiveness and benefit realization, not administrative cost reduction.