Program Life Cycle Management practice questions

Direct the component managers to resolve the issue independently.

Why it fails: The program manager is responsible for interdependency management.

Escalate the issue to the Program Sponsor immediately.

Why it fails: Escalation is a last resort; the program manager should attempt resolution first.

Cancel one of the component projects.

Why it fails: Cancellation is not a standard response to resource contention.

Conduct a project kickoff for the largest component.

Why it fails: Kickoffs occur after the program plan is established.

Release the initial program budget to the project managers.

Why it fails: Budget allocation occurs after detailed planning and component approval.

Develop the detailed Work Breakdown Structure for each project.

Why it fails: This is a project-level activity, not a program-level integration step.

Deny the request as the roadmap is already baselined.

Why it fails: Program management requires flexibility to address stakeholder needs if valid, but it must be processed through the correct channels.

Consult the project managers to see if the change is feasible.

Why it fails: Feasibility is a secondary consideration; the governance process takes priority first.

Update the roadmap immediately to satisfy the stakeholder.

Why it fails: Changing the roadmap without governance approval bypasses established procedures.

Program Roadmap.

Why it fails: The roadmap focuses on milestones and timelines.

Program Charter.

Why it fails: The charter authorizes the program, it doesn't plan for engagement.

Communication Matrix.

Why it fails: This is a component of the engagement plan, not the overarching document.

Communication Matrix

Why it fails: This is part of the communications plan.

Team Building

Why it fails: This is an activity, not a phase.

Financial Auditing

Why it fails: This is a process, not a phase.

Two projects using the same office space.

Why it fails: Operational, not a program-level dependency.

The project manager's vacation schedule.

Why it fails: Not a project dependency.

The local weather forecast.

Why it fails: Not a project dependency.

Vendor payroll spreadsheets

Why it fails: Vendor payroll spreadsheets are operational finance records, not primary components of the Program Management Plan. They support payment processing within procurement or finance functions; the programme plan addresses benefits realisation, governance structure, stakeholder engagement and transition planning.

Individual Project Task Lists

Why it fails: Individual project task lists sit at project level, below programme scope, and are not primary components of the Program Management Plan. They are used by project managers for scheduling and tracking; the programme plan instead covers benefits management, governance and stakeholder engagement.

Daily meeting minutes

Why it fails: Daily meeting minutes record operational progress and are not a primary component of the Program Management Plan, which defines governance, benefits, stakeholders and transition. Minutes belong to programme execution artefacts, such as the programme log or communications records, rather than the plan itself.

Transfer remaining program risks to the operations team.

Why it fails: Transferring remaining risks to operations is not a standard closure action. Risks should be closed, mitigated, or transitioned as part of benefit sustainment, but not simply transferred. Operations may assume some risks, but that is typically done during transition, not closure.

Update the Program Management Plan with lessons learned.

Why it fails: While lessons learned are captured during closure, updating the Program Management Plan is not a primary closure action. The plan is typically finalized and archived. Lessons learned are documented in the lessons learned register or final report, not necessarily in the plan itself.

Initiate new component projects to sustain benefits.

Why it fails: Initiating new component projects is not part of Program Closure; it would be part of program execution or a new program. Closure focuses on concluding existing activities, not starting new ones. Adding projects would extend the program and contradict the closure phase.

Program final report

Why it fails: The program final report is produced at the end of the program life cycle, during program closure. It summarizes performance and benefits realized. It is not an output of formulation, which occurs at the beginning of the program.

Benefits realization plan

Why it fails: The benefits realization plan is created during program planning and defines how benefits will be achieved, measured, and sustained. It is not the primary output of formulation, which focuses on authorizing the program and defining its strategic alignment.

Program management plan

Why it fails: The program management plan is developed during the program planning phase, not formulation. It details how the program will be executed, monitored, and controlled. While the charter is an input to the plan, it is not the primary output of formulation.

Close all component projects and release all program resources immediately.

Why it fails: Closing component projects and releasing resources should occur only after the transition is complete and benefits are successfully transferred. Doing so prematurely could jeopardize benefit realization and leave the operations team without necessary support during the transition.

Conduct a final program review to capture lessons learned and validate benefit achievement.

Why it fails: While a final program review is important, it is typically part of program closure rather than the transition of benefits. The transition focuses on transferring ownership and ensuring sustainment, not on retrospective analysis, which is more about closing the program.

Update the program charter to reflect the new operational responsibilities.

Why it fails: The program charter is a foundational document that authorizes the program and is not typically updated during transition. Operational responsibilities are documented in the benefits sustainment plan or transition plan, not the charter, making this activity inappropriate.

The level of authority and autonomy required to manage component projects and resolve conflicts.

Why it fails: Authority and autonomy are important aspects of governance, but they are derived from the program's strategic alignment and the need to manage interdependencies. This option is partially correct but not the primary consideration. The governance structure should first ensure alignment with organizational strategy and then define authority levels accordingly.

The preferences of the program sponsor and key stakeholders regarding reporting frequency.

Why it fails: Stakeholder preferences for reporting are important for engagement but are not the primary driver of governance design. Governance should be structured to enable effective decision-making and benefits realization, not merely to satisfy reporting preferences. Reporting frequency can be adjusted within the governance framework.

The number of component projects and their geographic distribution.

Why it fails: While geographic distribution and number of projects can influence governance, they are not the primary consideration. The primary focus should be on decision-making authority and accountability for program outcomes. Geographic factors may affect communication methods but do not fundamentally shape the governance framework's ability to manage interdependencies.

Conducting a program benefits realization review to confirm benefits are on track.

Why it fails: A benefits realization review is typically conducted during the benefits delivery phase and at program closure, not specifically during the transition phase. While it is important, the transition phase focuses on transferring ownership and ensuring operational readiness. The review may be part of the overall benefits management, but it is not an essential activity unique to transition.

Closing all component projects and releasing project resources.

Why it fails: Closing component projects and releasing resources is part of program closure, which occurs after transition. During transition, components may still be active to ensure smooth handover. Prematurely closing projects could disrupt the transition. The transition phase focuses on preparing operations to take over, not on administrative closure of projects.

Conducting a post-implementation review to evaluate program performance.

Why it fails: A post-implementation review is typically conducted after program closure to evaluate overall performance and benefits realization. While it may inform future programs, it is not an essential activity during the transition phase itself. The transition phase is about handover and readiness, not retrospective evaluation, which occurs later.

Releasing program resources and reassigning team members to other initiatives.

Why it fails: Releasing resources is a closure activity, but it is not one of the two most essential activities listed. It is important for cost management and resource optimization, yet it is operational and can occur after more critical closure tasks. The question asks for essential closure activities; resource release is a standard administrative step but not as critical as capturing lessons learned or obtaining final acceptance.

Initiating new component projects to address emerging business needs.

Why it fails: Initiating new component projects is a program formulation or benefits delivery activity, not a closure activity. During closure, the focus is on finalizing existing work, not starting new initiatives. Adding components at this stage would contradict the purpose of closure and could delay program completion. This option is clearly inappropriate for the closure phase.

Archiving program documents and updating organizational process assets.

Why it fails: Archiving documents and updating organizational process assets are important closure activities, but they are administrative and often performed after final acceptance and lessons learned. While they contribute to knowledge management, they are not among the two most essential activities in this context. The question emphasizes essential closure activities, and archiving is typically a follow-up step rather than a primary closure driver.

Initiating new component projects to sustain the benefits.

Why it fails: Initiating new projects is not part of program closure; it would extend the program or create a new one. Closure focuses on concluding existing activities and transitioning benefits. New projects should be part of a new program or portfolio, not the closing program.

Transferring all program resources to other programs without any assessment.

Why it fails: Resources should be released or transitioned based on a formal assessment and organizational needs. Unplanned transfer can disrupt other initiatives and is not a recommended closure activity. Proper resource release involves evaluating skills, timing, and organizational priorities.

Archiving program documents and making them accessible for future reference.

Why it fails: Archiving documents is a good practice but it is not one of the two most essential activities. It supports knowledge management but is secondary to performance review and final acceptance. Archiving is typically part of closure but not a primary focus compared to obtaining acceptance and capturing lessons.

The program charter

Why it fails: The program charter authorizes the program and outlines its initial scope and objectives, but it does not contain the detailed benefit realization metrics or the final performance data needed to verify that strategic objectives were met. While it provides the baseline, the program manager needs a document that tracks benefits and outcomes over time to conduct the final review.

The program management plan

Why it fails: The program management plan is a comprehensive document that describes how the program will be executed, monitored, and controlled. While it includes baselines and performance measurement criteria, it does not provide the actual realized benefit data needed to verify strategic objective achievement. At closure, the program manager needs a record of what was actually delivered and realized, not the plan for how it would be done.

The benefits realization plan

Why it fails: The benefits realization plan describes how benefits will be measured, tracked, and realized, but it is not the primary input for verifying that the program has met its strategic objectives at closure. It is a planning document; the actual verification requires comparing realized benefits against the plan, which is typically captured in the benefits register or a final benefits report.

Accelerate the component schedule.

Why it fails: Accelerating the schedule addresses the variance itself, not the benefits the component exists to deliver; benefits realisation analysis must first assess whether the delay threatens the expected benefits. Acceleration suits a component whose benefits depend on hitting an immovable external deadline.

Replace the component project manager.

Why it fails: Replacing the project manager addresses a personnel symptom, not the schedule variance threatening benefits realisation; the Program Manager must first assess the variance's impact on benefits. Replacement is tempting when a manager is genuinely underperforming, but that follows analysis, not precedes it.

Update the benefits realization plan.

Why it fails: Updating the benefits realisation plan is premature: the stem asks for the first step, which is assessing how the schedule variance affects benefit delivery. Plan revision is tempting because it is a legitimate program artefact, but it is the correct choice only once the variance's benefit impact is understood.

Component Charter

Why it fails: A component charter authorises and scopes an individual programme component; it does not itself demonstrate that the aggregated programme benefits trace to the organisation's strategic objectives. It is tempting because charters are genuine programme artifacts, and would be the right artifact when initiating or authorising a specific component within the programme.

Stakeholder Register

Why it fails: The stakeholder register records who is affected by or interested in the programme and how to engage them; it contains no linkage between programme benefits and strategic objectives. It is tempting because stakeholder analysis is a real programme planning activity, and would be correct when planning communications and engagement rather than strategic alignment.

Risk Register

Why it fails: The risk register documents identified threats, their probability, impact and responses; it does not map programme outcomes to strategic objectives. It is tempting because risk management is integral to programme planning, and would be the correct artifact when the question concerns uncertainty exposure rather than demonstrating strategic traceability.

Program Management Plan

Why it fails: The Program Management Plan is produced during the Program Definition phase, not Formulation, so it cannot establish strategic business value at formulation. It is tempting because it governs overall program execution, and would be the right artefact once the program has been formally defined and approved.

Program Roadmap

Why it fails: The Program Roadmap is created during the Program Definition phase to sequence benefits delivery, not during Formulation to establish strategic business value. It is tempting because it links projects to benefits over time, and would be correct when planning the delivery timeline after the business case is approved.

Benefits Realization Plan

Why it fails: The Benefits Realization Plan is produced later, during program definition and delivery, to track and measure benefit delivery; it does not establish strategic business value at formulation. It is tempting because benefits underpin value, but the formulation-phase document capturing strategic value is the program business case.

Business Case

Why it fails: The business case justifies the investment and expected benefits, but it does not confer formal authority; the program charter authorises the program's existence and names the program manager. A business case is the correct artefact earlier, when comparing options and securing funding approval.

Program Management Plan

Why it fails: The program management plan describes how the program will be executed, governed and controlled; it is developed after the program exists. The program charter is the instrument that formally authorises the program, so the plan cannot itself create that authority.

Program Roadmap

Why it fails: The program roadmap sequences projects, benefits and milestones over time; it is a planning artefact produced after authorisation. The program charter is the document that formally authorises the program and empowers the program manager, making the roadmap the wrong instrument for this purpose.

Reassign the technical lead to the program management office.

Why it fails: Permanently moving the technical lead into the PMO removes them from both projects, eliminating the shared capability the work depends on. It tempts because centralising scarce specialists under PMO control suits establishing standards or governance support, not delivering project tasks.

Prioritize the project with the highest budget.

Why it fails: Budget size does not resolve a shared technical lead's competing demands; the program manager should assess the dependencies against program benefits and re-sequence or negotiate capacity. Budget-based prioritisation is tempting where funding signals importance, but it ignores the resource constraint itself.

Escalate the issue to the program sponsor for immediate intervention.

Why it fails: Escalation hands the decision to the sponsor rather than resolving the dependency at program level, where the program manager owns cross-project resource arbitration. It tempts because sponsor intervention suits issues exceeding the program manager's authority, such as funding or scope conflicts.