Program Management Professional (PgMP) (PgMP) (PgMP) — Questions 1–75

The program roadmap is a high-level visual representation that communicates the program's vision, key milestones, and the planned sequencing of benefits delivery across the program life cycle. It aligns stakeholders on the overall direction and helps manage expectations about when benefits will be realized, making it the correct choice for this scenario.

A strategic alignment review is the appropriate first step because it systematically evaluates whether the program's objectives, components, and benefits still support the organization's new strategic direction. This review involves key stakeholders and provides the data needed to decide whether to continue, modify, or terminate the program. It ensures decisions are based on analysis rather than assumption, and it aligns with program management best practices.

Configuration Management identifies, documents and controls changes to programme scope, maintaining baselines and version control over scope statements and related artefacts. It satisfies the stem by governing every scope change through formal identification, documentation and management rather than ad hoc approval.

The roadmap communicates direction over time rather than detailed schedules, so it surfaces benefits, key milestones and project timelines together. This satisfies the stem's focus on what the roadmap primarily displays, distinguishing it from component-level plans.

At the initiation stage, the program manager should focus on stakeholder identification and analysis to understand who is impacted and what their needs are. Building relationships early fosters trust and facilitates later engagement. This aligns with the first steps of the stakeholder engagement cycle: identify, analyze, and plan. It sets the groundwork for a tailored engagement strategy that addresses diverse stakeholder concerns.

This is correct because benefits management involves managing interdependencies and trade-offs. The program manager must evaluate the impact of the tool on both benefits and make informed decisions. Adjusting the plan ensures that the overall benefit optimization is achieved. This aligns with PgMP's focus on balancing competing benefits and maintaining alignment with strategic objectives.

A program-level dependency map documents how component projects rely on each other's deliverables, milestones and resources, making cross-project sequencing visible. Creating it during planning satisfies the need to determine inter-project dependencies before scheduling and integration.

Assigning ownership to the operational entity transfers accountability for the benefit once the component project closes, satisfying the stem's requirement for sustained realisation. Documenting this in the Benefits Realization Plan ensures the transition is governed and measurable, preventing benefits from lapsing when project resources disband.

A stakeholder analysis helps the program manager understand the new executives' perspectives, priorities, and any concerns about the program. This insight is crucial for assessing political support and identifying potential champions or blockers. It also informs how to communicate the program's value and align it with the new strategic direction, ensuring that decisions consider stakeholder influence and interest.

A material change in an external assumption changes the benefit forecast, so the register and realization plan must be updated to keep them accurate. The program manager should also assess how the smaller penalty-avoidance benefit affects the overall benefits case and whether compensating benefits or re-planning are needed. This maintains informed governance without prematurely altering scope or closing the program.

This is correct because the benefits map directly links program outputs to strategic objectives. A benefits map that shows the CRM system increasing customer satisfaction scores demonstrates a clear line of sight from the program's deliverables to the strategic goal. It provides measurable evidence of alignment, which is a key criterion for assessing strategic alignment.

Benefit realisation measures and delivers the value the programme was created to produce, tracking whether expected benefits actually materialise after component projects deliver. It satisfies the stem by focusing on outcomes and value, not merely on completing deliverables or outputs.

A strategic alignment review re-evaluates the program's business case, benefits, and roadmap against the newly published enterprise strategy, giving governance the evidence it needs to continue, redirect, or terminate the program. This is the program manager's first responsibility because it frames all subsequent decisions and prevents the team from continuing to spend on a direction leadership may no longer want.

The program manager should first understand the root cause by reviewing performance data and collaborating with the project manager. This approach respects the project manager's autonomy while providing program-level support. It aligns with the program manager's role to monitor and control component projects without micromanaging.

Inadequate communication channels directly impede stakeholder engagement: information fails to reach the right people, expectations diverge and participation drops. This is a recognised engagement challenge, unlike scheduling or budgeting issues that belong to other performance domains.

Benefits delivery changes must be assessed against the business case before approval, because the change alters the expected benefits profile. Evaluating strategic alignment first gives the programme manager evidence to accept, reject or escalate, rather than implementing scope changes that undermine projected benefits.

The Steering Committee provides governance oversight, reviewing program direction and benefits against organisational strategy. This satisfies the stem's focus on strategic alignment by making that committee accountable for keeping the program's outcomes consistent with the organisation's strategic intent.

A what-if analysis allows the program manager to simulate the effects of resource changes on benefits delivery and strategic objectives. This data-driven approach enables informed recommendations, such as which components to accelerate, delay, or descope. It ensures that the program remains aligned with the new strategic initiative while minimizing negative impacts. This is the best approach because it balances the need to adapt with the need to preserve value.

The program manager should first review the misalignment and then take corrective action, which may include realigning the project's scope, updating the benefits register if the features provide value, or terminating the unauthorized work. This ensures the program remains focused on its strategic objectives and that benefits are properly tracked. It also engages governance for decisions on scope changes.

Assessing the impact on strategic alignment quantifies how the political risk affects the programme's intended benefits before any response is chosen. This satisfies the first-step constraint: impact assessment precedes mitigation planning, escalation, or risk register updates, ensuring decisions rest on evidence.

Program Formulation concludes with an approved, signed Program Charter that authorises the program and defines its benefits, scope and governance. This satisfies the stem's request for the phase's primary output, distinguishing it from the Program Definition phase that follows.

A final retrospective workshop directly satisfies the stem's constraint: incomplete lessons learned documentation. It captures tacit knowledge from team members through structured discussion before they disperse, producing the missing documentation as an output. Unlike passive archival methods, this active knowledge-transfer mechanism reconstructs undocumented insights while the team remains available.

The program manager should escalate to the full governance board because the chair's request conflicts with regulatory requirements. The board is responsible for ensuring that program changes comply with laws and regulations. A formal board decision will either confirm the need for compliance updates or provide documented rationale for an alternative approach, protecting the program.

Mapping program benefits to specific strategic objectives is essential because it explicitly shows how the program contributes to the organization's strategy. This mapping ensures that each benefit is tied to a strategic goal, providing traceability and justification for the program. It also helps in prioritizing components and making informed decisions about resource allocation. Without this mapping, the program may drift from its strategic purpose.

The Program Manager is a governance role because they own day-to-day programme delivery and report performance to the sponsoring body. This satisfies the stem's requirement, sitting within the governance structure alongside the sponsor and steering committee, accountable for executing decisions.

Risks evolve as components deliver and assumptions change, so periodic review of the program risk register keeps exposure current, retires closed risks and surfaces emerging ones. This satisfies the stem's requirement for ongoing program-level risk management rather than one-off identification.

This is the correct first step. The program manager should clarify the governance plan's reporting requirements and help the project manager understand why adherence is critical. By exploring barriers, such as perceived delays, the program manager can find solutions that maintain governance while addressing the project manager's concerns. This reinforces the process without resorting to escalation or discipline.

The program manager should first evaluate whether the requested features align with the program's intended benefits and strategic goals. This ensures that any changes do not deviate from the program's purpose and that resources are not diverted from realizing the planned benefits.

Scope changes outside the program mandate exceed the program manager's authority; the governance board owns strategic alignment decisions. Escalating there ensures the request is assessed against programme benefits rather than absorbed informally, preserving the approved scope baseline.

Benefit alignment governs component continuation, so the program manager formally reviews the project's ongoing contribution and transitions it out when benefits no longer accrue. This satisfies the stem's constraint that strong performance alone does not justify retention within the program.

Benefits-to-strategy mapping shows exactly where the program still contributes to digital self-service and workforce planning and where it does not. This gap analysis is the foundation for realignment because it converts the new strategy into specific changes to scope, components, and benefit targets, rather than leaving the program manager to guess which parts of payroll consolidation still matter.

Regulatory requirements are legally binding and supersede internal governance, so the manager must comply with them and record the deviation. Documenting the conflict preserves auditability and satisfies the obligation to escalate governance misalignment rather than silently ignore it.

This is the correct first step. The program manager should verify that the governance board has the authority to mandate such changes, as defined in the program charter and governance plan. Then, the change must be processed through the program's change control system to evaluate impacts on scope, schedule, cost, and benefits. This ensures the project manager's concerns are addressed while maintaining governance discipline.

New stakeholders identified during programme execution must be added to the plan with their engagement needs, otherwise they are omitted from communication and involvement activities. Addressing them satisfies the stem's requirement for an item that an update to the Stakeholder Engagement Plan should cover.

A performance gap analysis compares expected benefits against actual metrics and surfaces adoption barriers within the business unit. This diagnostic step precedes corrective action, ensuring the program manager addresses root causes rather than guessing at remedies.

Mapping both metric sets to higher-level program KPIs satisfies the stem's need for a unified dashboard across differing methodologies. Agile velocity and Waterfall earned value measure incompatible units, so aggregating them directly is meaningless; translating each into shared outcome measures such as benefits realisation, schedule confidence and cost performance enables consistent, comparable reporting at program level.

Formal evaluation tests the drifted scope against the program's strategic objectives, then realigns or adjusts the project accordingly. This satisfies the constraint that misalignment is strategic, requiring governance-level assessment rather than routine project change control.

Analysing root cause and evaluating governance impact directly satisfies the stem's requirement for a first governance response, since compliance failures signal a breakdown in oversight mechanisms rather than mere execution errors. This diagnostic step precedes corrective action, ensuring subsequent decisions address the underlying governance deficiency instead of treating symptoms.

Continuous engagement monitoring suits a volatile stakeholder landscape because it replaces static, one-off analysis with iterative cycles: feedback from each engagement updates the stakeholder register, influence and interest ratings, and the engagement strategy itself. This adaptive loop detects shifting coalitions and expectations early, satisfying the stem's volatility constraint where periodic reviews would lag behind.

Frequency defines how often each stakeholder group receives updates, letting the plan match cadence to information needs and governance reporting cycles. This satisfies the stem's requirement for a typical Stakeholder Communication Plan component alongside audience, channel and content.

The first step is to address the behavior directly with the person involved, clarifying the agreed communication channels and escalation path. This respects the relationship, gathers context about why the bypass occurred, and gives the supplier's project manager a chance to correct course before formal action. It also protects the program manager's credibility by resolving the issue at the lowest appropriate level.

New automation tools for production represent technological change in PESTLE, covering innovation and automation affecting operations. It satisfies the stem by being the factor driven by technological advancement rather than political, economic, social, legal or environmental forces.

Early communication of both the delay's impact and the mitigation plan gives stakeholders time to adjust their own plans and reduces speculation. This directly addresses the expectation-management constraint by replacing uncertainty with a clear, actionable picture before rumours fill the gap.

Benefits realization typically continues after the program closes, so business owners must take ownership of the remaining measures. Agreeing on reporting cadence, metrics, and escalation paths before closure keeps those stakeholders engaged and accountable. It also prevents a post-closure vacuum in which benefits erode unnoticed. This action sustains engagement by giving stakeholders a defined, ongoing role rather than an ending one.

Periodic project performance reports give the program manager scheduled visibility of each component's scope, schedule, cost and variance data. This satisfies the stem's monitoring requirement by supplying standardised, comparable metrics between reviews, enabling early detection of deviation from the program plan.

Mapping benefits to strategic goals ensures that the program delivers value that supports the organization's direction. The program sponsor, as the link to executive strategy, can confirm that the benefits are aligned and prioritized. This validation step is essential during benefits identification to avoid pursuing benefits that do not contribute to strategic objectives, which could lead to wasted resources and lack of support.

Critical success factors must trace to organisational strategy, because a program delivering outputs misaligned with strategic goals cannot realise intended benefits. This satisfies the stem's 'most critical' by making strategic alignment the governing criterion over tactical measures.

The benefit dependency map records each benefit, its owning project and its dependencies. Duplicate claims indicate an overlap, so reviewing the map identifies the conflict and lets the program manager reassign the benefit to a single owner, preventing double-counting in the program's benefit register.

Component drift is corrected by assessing each component against the program's benefits map and strategic objectives, then using governance to authorize scope corrections. This preserves the program manager's accountability for integration while respecting that component changes affecting the program baseline need formal approval. It also produces documented rationale for any descoping or realignment decisions.

The benefits register captures each benefit with its metric, baseline, target, and how and when it will be measured. For reduced onboarding time, this means the defined metric, the current baseline, the target to be achieved, and the measurement approach tied to a point in time. This is precisely the information that lets the program demonstrate realization after go-live rather than merely asserting it.

A benefits dependency analysis maps the relationships between project outputs, outcomes, and benefits. By tracing the process improvement initiative, the program manager can identify where the savings originate and assign ownership correctly, eliminating double-counting and ensuring accurate benefit reporting.

The Benefits Realization Plan is the governance artifact that defines how benefits will be measured, tracked, and reported throughout the program. It outlines metrics, baselines, targets, and ownership. Presenting this plan directly addresses the board's request and demonstrates alignment with program governance.

The benefits register maps each intended benefit to an owner, metric, and transition date, so the board can see whether component outputs are converting into compliance outcomes. It is the governance artifact that links deliverables to value realization and supports the board chair's question about collective outcomes rather than task completion.

Benefits unrealised because of market change cannot be delivered, so the program manager records them in the Final Program Report and transfers ownership to operations, which can monitor or pursue them post-closure. This satisfies the benefit transition requirement at program closure.

The phase-gate review is a governance checkpoint to evaluate whether the program should continue, be modified, or be terminated. It assesses readiness to proceed, including the status of benefits, risks, and stakeholder engagement. It also confirms that the program remains aligned with strategic objectives. This is the primary focus of a phase-gate review.

The benefits realization plan is the foundational document that defines the program's benefits, how they will be measured, when they will be realized, and how they will be sustained after program closure. It aligns component outputs with strategic benefits and provides the basis for benefit tracking and reporting. This is its primary purpose, making this option correct.

Benefits often materialise after programme closure, so accountability transfers formally to an operational owner who tracks and reports the remaining benefit. Retaining the programme team indefinitely is not standard, and abandoning the benefit forfeits the programme's justification.

This is correct because sustainment requires that the receiving organization can continue to manage and enhance the benefit. Providing training and resources to operations ensures they can maintain the LMS and keep content current, which is essential for sustaining improved skills. This aligns with PgMP's focus on transition and sustainment planning.

Tailoring the PMO's templates to meet the program's unique regulatory requirements ensures compliance while leveraging existing resources. Documenting the tailoring in the governance plan provides transparency and justification. This approach balances standardization with flexibility, which is a key principle in program governance. It also ensures that the governance framework is fit for purpose and auditable.

Clear decision rights and escalation thresholds enable the PGB to focus on strategic decisions while delegating operational matters appropriately. This reduces bottlenecks and ambiguity, allowing components to proceed within defined boundaries. It directly supports effective governance by clarifying who decides what and when escalation is required, which is a foundational element of the program governance performance domain and improves both speed and accountability.

The stakeholder register and analysis are the primary inputs because they identify stakeholders, their interests, influence, and engagement needs. This information is essential to tailor engagement strategies. Without a thorough understanding of stakeholders, the engagement plan cannot be effective.

A decrease in energy consumption directly supports the strategic goals of sustainability and reducing carbon footprint. By prioritizing this benefit, the program manager ensures that the program contributes to the organization's strategic objectives. This alignment increases the program's perceived value and helps secure stakeholder support. It also provides measurable outcomes that can be tracked in the benefits realization plan.

The Program Charter is the authorising document that records the program's strategic outcomes and the performing organisation's commitment to them. It satisfies the stem by serving as the primary agreement linking program delivery to those strategic outcomes.

Escalating immediately with an impact analysis allows the governance board to fulfill its oversight role and make informed decisions about how to adapt the program to the new regulation. This ensures that any changes to scope, schedule, budget, or risk are approved at the appropriate level. Timely escalation also demonstrates transparency and proactive risk management, which are essential for program governance.

Benefits mature on different timelines, so each benefit needs its own measurement points aligned to when value is expected. Immediate compliance benefits are verified at go-live, while market share growth is tracked at intervals across the maturation period. This tailored approach provides timely evidence of realization and early detection of drift, which a uniform schedule cannot deliver.

The benefits register records each benefit together with its assigned owner, metric, baseline, and target. Naming a benefit owner per benefit creates clear post-program accountability that persists after the program closes, because the owner is an operational role rather than a temporary program role. This directly answers the sponsor's request for documented accountability for each benefit.

Benefits sustainment requires that accountability for continued measurement moves from the program to the business once components are embedded. Transferring each benefit, along with its metric, target, and review cadence, to the designated benefit owner ensures tracking continues after the program closes. This is the standard closure action that prevents benefits from being orphaned when the program team disbands.

ROI analysis validates the Program Business Case by quantifying projected financial return against investment, confirming the programme remains viable and aligned to strategic objectives. This satisfies the stem's validation requirement, providing the economic justification governance needs before authorising continued funding and resource commitment.

Return on Investment directly quantifies financial return against program cost, satisfying the stem's demand for strategic value at organisation level. Unlike delivery-focused metrics such as schedule variance or defect rates, ROI expresses benefit in monetary terms executives use for portfolio decisions, making it the strongest evidence that the program's outcomes justify continued investment.

A benefit must be measurable to be managed. Defining a metric, baseline, and target makes the benefit actionable and allows the program to track progress. The benefits register should contain this information for each benefit. Without it, the program cannot demonstrate whether productivity improved or whether the collaboration platform delivered value.

Delegated authority is defined by both financial thresholds and the nature of the change. A regulatory compliance impact affecting multiple components is a strategic issue that exceeds a purely financial delegation. Escalating to the PGB ensures the decision is made at the appropriate governance level, maintains compliance, and preserves the integrity of the governance framework. This action also documents the boundary violation for future delegation clarity.

Documenting the breach preserves an audit trail, while engaging the executive directly repairs the governance gap that permitted the bypass. This satisfies the stem's constraint: the manager must correct the escalation route without alienating the senior stakeholder whose sponsorship the program depends on. Addressing the process gap prevents recurrence rather than merely punishing the individual.

The program manager must formally assess the impact of the strategic pivot and update the foundational documents that justify and guide the program. Updating the business case, benefits register, and roadmap ensures the program remains aligned with the new subscription-based revenue strategy and provides a basis for decisions on scope, funding, and priorities. This action also engages the program sponsor and governance board appropriately.

The Program Charter formally authorises the programme and grants the programme manager authority to apply organisational resources, satisfying the stem's requirement for primary authorisation to commence. Issued by the sponsoring executive, it distinguishes the programme from its constituent projects, each of which receives authorisation separately through its own project charter.

The power/interest grid classifies stakeholders by their authority over program outcomes and their level of concern, which directly determines how much engagement effort each group needs. In a multi-year program with conflicting priorities across five units, this classification helps the program manager allocate limited engagement resources where they matter most, forming a rational foundation before deeper strategies are developed.