PGMP practice question 18 of 35

A software development program will launch iterative versions of new software called Alpha over two years. Following that, a program will be released…

Full set: 452 questions
A software development program will launch iterative versions of new software called Alpha over two years. Following that, a program will be released to the program team and developers to create new software called Bet a. While the program manager prepares the program closure plan for Alpha, the program sponsor expresses concern about its support after program closure. What should the program manager do as part of Alpha’s program closure plan?
Answer options
A: Execute the transition plan, and include knowledge transfer to transition Alpha support to operations. Correct answer
B: Keep the Alpha program open until support is no longer required, then execute program closure.
C: Adjust Alpha’s exit criteria to ensure its support is included in the Beta program.
D: Document the program closure procedure to ensure that resources are released from Alpha to develop Beta.
Correct Answer:
A. Execute the transition plan, and include knowledge transfer to transition Alpha support to operations.
Explanation

According to the PMI Standard for Program Management, a critical activity within the Program Closure Phase is the formal transition of the program's outputs and benefits to the sustaining organization, which is typically the operations department. The program manager's responsibility is to ensure that a comprehensive transition plan is executed. This plan must include knowledge transfer, documentation, and processes for ongoing support to guarantee that the benefits delivered by the program (the Alpha software) can be sustained post-closure. This directly addresses the sponsor's concern about long-term support.

Why Incorrect

B. Keep the Alpha program open until support is no longer required, then execute program closure. Programs are temporary endeavors with defined start and end dates. Ongoing support is an operational function, and keeping a program open indefinitely for this purpose violates fundamental program management principles.
C. Adjust Alpha’s exit criteria to ensure its support is included in the Beta program. This is incorrect because the responsibility for sustaining the benefits of one program should not be transferred to another new, temporary program. Operational support for Alpha is an operational function, not a component of the Beta development program.
D. Document the program closure procedure to ensure that resources are released from Alpha to develop Beta. While releasing resources is a part of program closure, this action focuses on administrative closure and resource allocation. It does not address the sponsor's specific concern regarding the ongoing support and sustainment of the Alpha software.

References

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.).

Section 5.5

Program Transition and Closure: This section states

"This domain involves the activities performed to transition the program benefits to the sustaining organization and formally close the program." (p. 89). This supports the idea that transition to a sustaining entity (operations) is the correct procedure.

Section 3.5.5

Program Closure Phase: This section details the activities of the phase

including

"During this phase

program managers are responsible for... finalizing the transition of benefits to the sustaining organization

and ensuring that benefit sustainment plans are in place and are being executed by the sustaining organization." (p. 41). This directly aligns with option A.

2. Thiry

M. (2015). A Framework for Value Management Practice. In Program Management: A Life Cycle Approach (pp. 1-23). John Wiley & Sons

Inc.

This academic text emphasizes that program closure involves a structured handover to ensure benefits are sustained. It states

"The program closure is not the end of the benefits; it is the moment when the business takes over the sustainment of the benefits." This reinforces that responsibility shifts to the business/operations

not another program.

Scroll to Top