25 Questions — PMI – PgMP : Certified Program Management Professional - Domain 2 - Program Life Cycle Management

Expand any question to reveal the correct answer and explanation.

1. 1 A program manager is in the program formulation phase and is defining the program's architecture. A key stakeholder insists on initiating a high-priority component project immediately to capitalize on a market window. Why should the program manager resist this until the program definition is more mature?

   Consider the primary difference between managing a collection of projects and managing a program.

   Initiating components before defining the program architecture risks producing outputs that do not align with the program's intended strategic benefits.

   Program formulation ensures that every project is specifically designed to contribute to the collective value and strategic goals of the program.

   • ✗ The project manager for the component has not yet been hired or assigned by the program office.

     While staffing is important, the strategic risk of misalignment is the primary concern during the definition phase.

   • ✗ Project initiation requires a separate charter that can only be written after the program roadmap is $100\%$ complete.

     Charters can be drafted earlier, but the concern is the lack of a guiding architecture rather than a documentation sequence.

   • ✗ The project management information system (PMIS) must be fully operational before any component work begins.

     The PMIS is a support tool, but its absence does not inherently cause strategic misalignment of project outputs.

2. 2 During the program planning phase, the program manager discovers that two projects require the same specialized testing laboratory at the same time. What is the most effective program-level integration action?

   Think about how a program manager balances competing needs to maximize total value.

   Perform resource leveling and optimization across the program to align laboratory access with the timing of critical benefit milestones.

   Program-level resource management focuses on optimizing shared resources to ensure the overall program schedule and benefits are protected.

   • ✗ Instruct the project managers to negotiate a schedule between themselves and inform the program office of the outcome.

     This abdicates the program manager's responsibility for cross-project integration and resource optimization.

   • ✗ Allocate the laboratory to the project with the largest budget to protect the organization's biggest financial investment.

     Resource allocation in programs should be based on benefit priority and strategic alignment, not individual project budgets.

   • ✗ Cancel one of the projects to eliminate the resource conflict and simplify the program roadmap.

     Cancellation is a drastic measure that should only occur if a project no longer contributes to strategic benefits, not just for a scheduling conflict.

3. 3 An organization is transitioning to the Fifth Edition of the Standard for Program Management. How does the current view of Integration Management differ from the Fourth Edition?

   Consider the shift from a process-centric model to a principle-led model in the latest standard.

   Integration is now viewed as a continuous activity that connects all performance domains rather than being localized within the Life Cycle domain.

   The Fifth Edition emphasizes that integration is an ongoing responsibility that links strategic alignment, governance, and benefits delivery throughout the program.

   • ✗ Integration has been removed as a program activity and is now handled exclusively at the portfolio level.

     Integration remains a core program management function, though its conceptual positioning has shifted.

   • ✗ Integration is now strictly a technical function performed by the Project Management Office (PMO) rather than the program manager.

     Integration management is a leadership and coordination role central to the program manager's responsibilities.

   • ✗ Integration is now only required during the Program Closure phase to ensure all projects finish at the same time.

     Integration is required across all phases to manage interdependencies and ensure benefits realization.

4. 4 A program manager is overseeing the benefits delivery phase of a global HR transformation program. A project manager reports a major delay in a payroll system project. What is the program manager's primary responsibility in this scenario?

   Focus on the 'orchestration' aspect of program management.

   Analyze the impact of the delay on other interdependent projects and the timing of related program benefits.

   The program manager's role is to manage the 'white space' between projects, ensuring that delays in one component don't cause a cascade of failure across the program's value chain.

   • ✗ Take over direct management of the payroll project to ensure it gets back on track immediately.

     The program manager should maintain a strategic oversight role and not perform the tactical duties of the project manager.

   • ✗ Update the project-level risk register and wait for the project manager to resolve the issue.

     Program managers must actively manage inter-project dependencies rather than passively waiting for project-level resolutions.

   • ✗ Allocate the entire program contingency reserve to the payroll project to hire more contractors.

     Reserves should be used based on a formal impact assessment and in accordance with established governance thresholds.

5. 5 During the closure of a multi-year infrastructure program, the program manager realizes that although all project deliverables are complete, the operational team is not ready to accept the handover. What essential program life cycle task was likely missed?

   Identify the bridge between the program's end and the start of ongoing operations.

   Developing a comprehensive benefits transition and sustainment plan early in the program lifecycle.

   Success in program management is defined by the successful transition of capabilities into operations to ensure long-term benefit realization.

   • ✗ Closing the project-level contracts with external vendors once the physical work was finished.

     Contract closure is a tactical activity and does not address the operational readiness for benefits sustainment.

   • ✗ Conducting a final performance review for the project managers involved in the program.

     While part of closure, this does not facilitate the operational adoption of the program's outputs.

   • ✗ Obtaining a sign-off on the final project budget from the finance department.

     Financial closure is necessary but does not guarantee that the organization can actually use the deliverables to create value.

6. 6 In a program with $3$ interdependent projects, Project $A$ produces a software engine, Project $B$ develops the user interface, and Project $C$ handles data migration. If Project $A$ is delayed by two weeks, what is the best integration response by the program manager?

   Look for an answer that involves re-aligning the collective components.

   Evaluate the program roadmap and adjust the start dates of Projects $B$ and $C$ to minimize idle time and resource waste.

   Managing interdependencies involves dynamically adjusting the roadmap to maintain synchronization across all program components.

   • ✗ Instruct Projects $B$ and $C$ to continue working at full speed to show the sponsor that only one project is failing.

     This approach ignores interdependencies and leads to wasted effort if the later projects cannot integrate with the delayed output.

   • ✗ Merge all three projects into a single large project to eliminate the need for interdependency management.

     Merging projects does not remove the underlying technical dependencies and usually increases management complexity.

   • ✗ Ask the Project $A$ manager to work overtime without providing any additional program-level support.

     This is a tactical project-level reaction and does not address the broader programmatic integration needs.

7. 7 Which of the following activities is a primary component of the Program Formulation sub-phase within the Program Definition phase?

   Think about the very first steps taken to justify and initiate a large-scale initiative.

   Developing the program business case and establishing the program charter to authorize the program's existence.

   Program formulation focuses on the high-level vision, mission, and justification for the program before detailed planning begins.

   • ✗ Managing the day-to-day execution of component projects and tracking their individual deliverables.

     This activity belongs to the Benefits Delivery phase, not the initial Definition phase.

   • ✗ Executing the transition plan to hand over benefits to the functional organization.

     Transition activities occur during the Program Closure phase.

   • ✗ Performing a final audit of all procurement contracts to ensure legal compliance.

     Audits are typically part of the Monitoring and Controlling or Closure activities, not the initial formulation.

8. 8 A program manager is managing a complex program where two component projects are producing overlapping deliverables. What is the most appropriate action to maintain program-level efficiency?

   Consider the program manager's role in optimizing the collective output of the components.

   Coordinate with the project managers to rationalize the scope and remove the duplication across the projects.

   Removing duplication and ensuring efficient resource use is a core integration responsibility of the program manager.

   • ✗ Allow both projects to continue as planned to provide a backup in case one project fails.

     Intentionally allowing duplication is inefficient and contradicts the goal of generating synergy within a program.

   • ✗ Decide which project is 'better' and cancel the other project immediately without further analysis.

     The decision should be based on a scope rationalization and impact analysis, not a subjective preference.

   • ✗ Escalate the duplication to the corporate legal department to check for internal copyright issues.

     While legal compliance is important, duplication between internal projects is a management and coordination issue, not a legal one.

9. 9 When defining the program roadmap, what is the primary purpose of identifying 'key decision points' or 'phase gates'?

   Think about the role of the Steering Committee or Governance Board at these intervals.

   To provide structured opportunities for the governance board to validate strategic alignment and authorize the program to proceed to the next phase.

   Phase gates act as control points where the program's continued viability and alignment with organizational goals are assessed.

   • ✗ To create mandatory break periods for project teams to prevent burnout during long programs.

     While breaks are important, the primary purpose of a gate is governance and strategic control.

   • ✗ To allow the program manager to rewrite the business case from scratch every few months.

     Business cases are validated at gates, but they should not be fundamentally rewritten unless the strategic environment has changed.

   • ✗ To ensure that all project managers have submitted their weekly status reports on time.

     Status reporting is a tactical monitoring activity, whereas gates are strategic decision points.

10. 10 During the Program Benefits Delivery phase, the organization's strategic priorities shift due to a new environmental regulation. How should the program manager respond within the program life cycle?

    Consider the program manager's responsibility for 'strategic alignment' throughout the lifecycle.

    Conduct an impact assessment on the program's roadmap and benefits realization plan, then recommend necessary adjustments to the governance board.

    Programs are dynamic; the program manager must continuously scan the environment and align the program's life cycle with shifting corporate goals.

    • ✗ Ignore the regulation and continue with the original plan to ensure the program finishes on time and within budget.

      Finishing on time is useless if the program no longer provides the required strategic value or is non-compliant.

    • ✗ Immediately stop all projects and wait for the executive leadership to provide a new set of instructions.

      The program manager should proactively analyze the situation and provide recommendations rather than passively stopping all work.

    • ✗ Tell the project managers to incorporate the new regulation into their projects without changing the program-level milestones.

      Major strategic shifts usually require adjustments to the program-level roadmap and schedule to remain realistic.

11. 11 A program manager is establishing a program-level change governance process. Which of the following changes MUST be approved at the program level rather than the project level?

    Think about the boundary between project authority and program authority.

    A change in a project's technical approach that alters a critical interdependency with another component project.

    Changes that impact other projects, the program's architecture, or its ability to deliver strategic benefits require program-level oversight.

    • ✗ A request to change the color scheme of a project's internal status dashboard.

      Minor project-level aesthetic choices do not typically impact the program's strategic delivery or interdependencies.

    • ✗ The replacement of a junior developer on a project team with a developer of equal skill.

      Standard project-level staffing changes are usually managed by the project manager unless it involves a shared program-level resource.

    • ✗ A decision to move a weekly project team meeting from Tuesday to Wednesday.

      Tactical project meeting schedules do not require program-level governance approval.

12. 12 In the context of the Program Life Cycle, what is the 'program master schedule'?

    Identify the artifact that provides the 'big picture' timeline of the program.

    An integrated document that aggregates the schedules of all component projects and program-level activities to show the path to benefit realization.

    The master schedule is the primary integration tool for tracking the timing of all program components and their interdependencies.

    • ✗ A list of the vacation schedules for every project manager in the program.

      While resource availability is important, the master schedule's focus is on project work and milestones.

    • ✗ A collection of independent project schedules that the program manager keeps in a single folder but does not link.

      A master schedule must be integrated and reflect interdependencies to be an effective program management tool.

    • ✗ The payroll schedule for the entire company, including staff not involved in the program.

      This is a corporate administrative document, not a program management artifact.

13. 13 A program manager is transitioning a program's benefits to the operational environment. Which of the following is the most critical document to hand over to the operational managers?

    Focus on the artifact that ensures the program's 'legacy' is preserved.

    The benefits sustainment plan and the benefits register, which detail how the realized value will be maintained and measured over time.

    Operational teams need clear guidance on how to continue tracking and protecting the value created by the program after it closes.

    • ✗ The original resumes of all the project managers who worked on the program.

      Resumes are irrelevant to the ongoing operational sustainment of program benefits.

    • ✗ A list of all the deleted files from the project management information system.

      Archival data management is part of closure, but it does not aid in the sustainment of operational benefits.

    • ✗ The internal budget codes used by the finance department during the planning phase.

      While useful for accounting, this does not support the functional sustainment of the program's outcomes.

14. 14 During the Program Planning phase, why is it necessary to develop a Program WBS (Work Breakdown Structure) in addition to project-level WBSs?

    Consider the activities that only the program manager and program office perform.

    To identify and plan for program-level activities, such as governance, integration, and stakeholder management, that are not captured within individual projects.

    A program involves work that exists 'above' the project level, which must be explicitly planned and resourced.

    • ✗ To double-check the work of the project managers and ensure they haven't made any spelling errors in their project plans.

      The Program WBS is a tool for programmatic scope management, not a proofreading exercise.

    • ✗ Because the PMI standards require exactly two levels of WBS for every initiative, regardless of size.

      There is no rigid 'two-level' rule; WBS structures are tailored to the needs of the program's complexity.

    • ✗ To replace all project-level WBSs so that the program manager has total control over every single task.

      The Program WBS complements project-level structures rather than replacing them, allowing for distributed management.

15. 15 A program manager is closing a program after successful transition. What should be done with the 'lessons learned' captured throughout the program life cycle?

    Think about the 'Giving Back to the Profession' concept in certification maintenance.

    They should be archived in an organizational knowledge repository to improve the success rate of future programs and projects.

    A key part of program closure is contributing back to the organization's intellectual capital to support continuous improvement.

    • ✗ They should be deleted to prevent future program managers from making the same mistakes and becoming over-confident.

      Lessons learned are valuable assets and should never be deleted; they provide the basis for organizational learning.

    • ✗ They should be given only to the program sponsor as a confidential 'confession' of what went wrong.

      While sponsors review them, lessons learned are intended for broad organizational use to improve professional practice.

    • ✗ They should be framed and hung in the lobby to celebrate the program's completion.

      This is a symbolic act, but archiving them for practical use is the required professional activity.

16. 16 During the benefits delivery phase, a project manager escalates a resource conflict that is impacting their project's ability to deliver a critical component. The program manager realizes this component is a prerequisite for a benefit in another project. What is this an example of?

    Look for a term that describes the 'linkages' between different parts of the program.

    Managing cross-project interdependencies to ensure the program's critical path to benefit realization is maintained.

    A core lifecycle task is identifying and resolving conflicts that threaten the flow of outputs between projects.

    • ✗ Scope creep at the project level that is causing unnecessary delays in the program.

      A prerequisite dependency is a planned relationship, not necessarily an example of uncontrolled scope expansion.

    • ✗ A failure of the program governance board to authorize sufficient funding for the program.

      Resource conflicts are common in execution and do not inherently mean that the initial funding was inadequate.

    • ✗ Micromanagement by the program manager who is interfering in project-level resource allocation.

      Resolving escalated cross-project conflicts is a legitimate and necessary program management responsibility.

17. 17 When a program enters the 'Program Closure' phase, what happens to the program's governance structure?

    Consider when the program manager's authority actually ends.

    It remains active to oversee the final administrative activities, benefit transitions, and the formal disbanding of the program team.

    Governance is required until the program is officially terminated to ensure accountability during the wind-down process.

    • ✗ It is immediately disbanded the moment the last project deliverable is finished.

      Administrative and transition activities still require oversight and decision-making authority.

    • ✗ It is transferred to the operational manager who will be using the program's outputs.

      Operational managers may have their own governance, but program governance is specific to the life cycle of the program itself.

    • ✗ It is upgraded to a 'Portfolio Steering Committee' to manage all other programs in the company.

      While individuals may move, the specific governance structure for the closing program is retired.

18. 18 A program manager is conducting an environmental scan mid-way through the benefits delivery phase. They find that a competitor has launched a product that makes the program's primary objective obsolete. What is the most appropriate lifecycle action?

    Think about the 'sunk cost fallacy' versus 'strategic alignment'.

    Present the findings to the program steering committee and recommend either a major re-scoping or the premature closure of the program.

    If a program can no longer deliver strategic value, governance should decide whether to pivot or stop the investment.

    • ✗ Keep the information secret to avoid alarming the project teams and ruining morale.

      Withholding strategic information is a breach of professional ethics and leads to wasted organizational resources.

    • ✗ Accelerate all projects to finish before the competitor can gain more market share.

      If the objective is truly obsolete, accelerating the delivery of a worthless product is a waste of time and money.

    • ✗ Sue the competitor for infringing on the program's roadmap ideas.

      This is a legal strategy and does not address the fundamental management problem of the program's lost strategic value.

19. 19 In program management, what is the 'Integration' performance domain (specifically in the context of the 5th edition) primarily concerned with?

    Focus on the 'holistic' view of the program.

    Connecting and harmonizing all performance domains, program components, and activities throughout the program's lifecycle.

    Integration is the glue that ensures all parts of the program work together as a unified system to deliver value.

    • ✗ The technical process of merging software code from two different development teams.

      This is a technical project-level task, not the broad strategic integration managed at the program level.

    • ✗ Ensuring that the program manager has a single email inbox for all project communications.

      Integration refers to the coordination of management activities and strategic objectives, not personal organization.

    • ✗ Combining the budgets of all projects into a single bank account for easier tracking.

      While financial integration is part of it, integration encompasses all areas of program management, including risk, scope, and stakeholders.

20. 20 During the Program Definition phase, the program manager establishes the program charter. Which of the following best describes the purpose of this document?

    Think about what the program manager needs before they can start spending money or directing teams.

    To formally authorize the program and provide the program manager with the authority to use organizational resources to achieve the program's goals.

    The charter is the official birth certificate of the program, establishing its scope, objectives, and leadership authority.

    • ✗ To list the exact daily tasks of every team member for the next three years.

      A charter is a high-level document; detailed task lists are part of project-level planning in the delivery phase.

    • ✗ To serve as a legally binding contract between the program manager and the project managers.

      The charter is an internal authorization document, not a commercial contract between employees.

    • ✗ To act as a press release for the external media to announce the organization's new strategy.

      While it can inform communications, its primary purpose is internal governance and authorization.

21. 21 A program manager is managing the transition of benefits for a new public transportation system. One of the projects—the fare-card system—is finished, but the station construction project is delayed by six months. How does this impact the program's life cycle?

    Consider the dependency between the 'output' of one project and the 'outcome' of the program.

    The benefits associated with the fare-card system cannot be fully realized until the stations are complete, requiring an adjustment to the program's transition schedule.

    Program benefits often depend on the integration of multiple project outputs; the delay of one can prevent the realization of others.

    • ✗ The fare-card system should be launched anyway to show the public that the program is partially successful.

      Launching a fare-card system without stations is unlikely to provide any actual benefit and may cause stakeholder frustration.

    • ✗ The program should be closed immediately, and the fare-card project should be treated as a separate success.

      Program closure requires the transition of the collective benefits, which are currently at risk due to the station delay.

    • ✗ The program manager should fire the station construction manager to set an example for the fare-card team.

      This is a reactive personnel action that does not address the underlying strategic scheduling and benefit realization problem.

22. 22 Why is 'Program Integration' considered more complex than 'Project Integration'?

    Think about the scope and level of authority involved.

    Because it requires managing dependencies and conflicts across multiple, often shifting, projects and organizational boundaries to achieve a strategic goal.

    Program integration deals with higher levels of ambiguity and broader cross-functional interactions than single-project integration.

    • ✗ Because the program manager has to use more expensive software than the project managers.

      The complexity is inherent in the scope and scale of the work, not the cost of the tools used.

    • ✗ Because it involves managing thousands of small tasks instead of just a few hundred.

      While scale is a factor, the fundamental difference is the strategic and interdependent nature of the work, not just the volume of tasks.

    • ✗ Because program managers are required to attend more meetings than project managers.

      Meetings are a symptom of coordination needs, but the complexity stems from the strategic alignment of diverse initiatives.

23. 23 During the Benefits Delivery phase, the program manager identifies a risk that a critical vendor for one of the projects might go bankrupt. What is the correct programmatic response?

    Consider the program-level 'view' of risk.

    Assess the risk's impact on the entire program's benefits and roadmap, and develop a coordinated mitigation strategy that might involve multiple projects.

    Program risk management involves looking at how project-level risks aggregate and impact the program's overall strategic success.

    • ✗ Wait for the project manager to handle it, as vendors are strictly a project-level concern.

      If the vendor is critical to the program's benefits, the program manager must be involved in the risk response.

    • ✗ Immediately cancel the contract and find a new vendor without consulting the project manager.

      This bypasses project-level authority and could cause more disruption if not coordinated with the project team.

    • ✗ Lend the vendor money from the program's management reserve to keep them in business.

      Program funds are intended for program activities and risk mitigation, not for corporate bailouts of external vendors.

24. 24 As a program transitions into the 'Program Closure' phase, what is the primary purpose of the final 'Program Performance Analysis Report'?

    Identify the primary metric of success for a program.

    To document the extent to which the program achieved its strategic objectives and delivered its planned benefits compared to the original business case.

    The final evaluation of a program is based on its ability to realize the value that justified its existence in the first place.

    • ✗ To provide a list of all the pizza parties held for the project teams during the execution phase.

      Administrative celebrations are not part of the formal performance analysis of the program's strategic objectives.

    • ✗ To rank the project managers from 'best' to 'worst' to determine their next assignments.

      Performance analysis focuses on the program's outcomes, not on individual performance appraisals.

    • ✗ To prove to the auditors that no money was spent on unapproved office supplies.

      This is a matter of financial auditing, not programmatic performance analysis relative to strategic goals.

25. 25 A program manager is in the program planning sub-phase. They are developing a 'high-level milestone plan'. How does this plan differ from a project schedule?

    Think about 'coordination' and 'strategic oversight'.

    It focuses on the timing of major program-level events, benefit realizations, and critical cross-project dependencies rather than granular tasks.

    The milestone plan provides a strategic overview of the program's progression toward its ultimate value targets.

    • ✗ It is exactly the same as a project schedule but it is printed on larger paper.

      The difference is one of scope and strategic focus, not physical presentation.

    • ✗ It only includes the dates for the program manager's own meetings and excludes all project work.

      A milestone plan must capture the major outputs of the constituent projects that lead to benefit realization.

    • ✗ It is a secret document that only the program sponsor is allowed to see.

      The milestone plan is a core communication and alignment tool for all major stakeholders.