When should a program manager approve the closure of a component project?

Question

Options

• AWhen acceptance criteria of the project are met
• BWhen the project has delivered the project benefits
• CWhen program deliverables are complete
• DWhen project deliverables are complete

• A
  5% (1)
• B
  11% (2)
• C
  79% (15)
• D
  5% (1)

Explanation

A component project exists to contribute to program-level deliverables, not to stand alone. The program manager approves component closure when the program deliverables - those that the component was established to produce - are complete and accepted. This distinction is critical: a component project may finish its own internal deliverables (option D) while integration into the broader program deliverable is still incomplete. Closing based solely on project-level acceptance (A) or project benefits (B) misses the program manager's broader perspective. Only when the component's contributions have fully materialized as program-level outcomes is closure appropriate from a program governance standpoint.

No community discussion yet for this question.