Program closure deliverables and objectives

Artifact/Deliverable

Required or optional
Methodologies are a tool box comprised of processes, guidelines, techniques, software, and templates.  The tools and how they are used are selected to fit the program so that the risks, benefits, and complexities can be appropriately managed for that unique program.  The chart below outlines program management deliverables and tools that can be used in program closure.  An 'x' indicates that deliverable or template is highly recommended.  

Lessons learned summary

(last revised Aug 17, 2015)
x

Closure report

(last revised Sep 4, 2015)
x
Closure meeting x

    The program closure phase objectives include:

    • acknowledge program completion, with a final Sponsor sign off/acceptance of deliverables and benefits
    • assess program success
    • identify, document, and share best practices and lessons learned with other projects and programs
    • release the program team
    • provide an opportunity to thank the program team for their efforts and congratulate them on their accomplishments
    • provide an opportunity for final program communications to stakeholders and others interested in the program
    • transition any remaining deliverables to operations
    • transition outstanding issues and benefit measurements to operations
    • forward future initiatives and projects into ideation and intake processes
    • provide feedback into continuous improvement of program management methodology
    • update the program and portfolio information
    • archive program management artifacts

    Projects that were executed as components of the program will have completed their own project closure.  The program can not close until all components within the program have closed.

    The closure phase stages the final deliverables for ongoing operations.

    PMO services to support project closure

    • Facilitation and/or consulting towards:
      • issuing satisfaction survey and providing the anonymous responses
      • lessons learned collection and documentation
      • program success measures
      • closure report
    • A closure meeting to:
      • share program experiences for continuous improvement into program management processes
      • share business experiences
      • answer any questions and offer assistance
      • discuss program success and how PMG may help future programs
      • update the program and portfolio information
      • understand how closure of this program enables other portfolio projects or programs
      • discuss recommendations the PMG may assist with implementing
      • bring forward future initiatives and projects
      • discuss benefit realization
      • archive program management artifacts

    To request these services, please submit an RT to the IST-PMG RT queue (online or  email).