Project+/Closing
From Wikibooks, open books for an open world
< Project+
This page may need to be Contents
- 1 Project Close Out Phase
- 1.1 Closing
- 1.2 Output
- 1.3 Formal Acceptance Of The Project By The Customers
- 1.4 Project Review
- 1.5 Project Archives
- 1.6 Ongoing Maintenance Should Be Discussed In A Project Close Out Meeting
- 1.7 Executive Sponsor Is Responsible For Authorizing Closure Of The Project
- 1.8 All Contract Files Must Be Closed Out
- 1.9 Lessons Learned Report
- 1.10 Project Audit
Project Close Out Phase[edit]
Closing[edit]
- process of gaining formal acceptance for the results of a project or phase.
- bringing project or phase to an orderly end.
- archiving of project information and post-project review.
Output[edit]
- project archives
- formal acceptance documentation
- project review
- team member evaluations
- lessons learned report = last deliverable
Formal Acceptance Of The Project By The Customers[edit]
- first step in close out phase
- a goals of the close out phase?
- formal acceptance documentation should be prepared
- PM should document customer acceptance
Project Review[edit]
- necessary task in preparation of the Close Out phase
- asses and evaluate each phases of the project
- asses and evaluate the overall project performance
- a way to learn from the experience and continuously improve project performance
Project Archives[edit]
- leave clear and complete documentation of the project
Ongoing Maintenance Should Be Discussed In A Project Close Out Meeting[edit]
Executive Sponsor Is Responsible For Authorizing Closure Of The Project[edit]
All Contract Files Must Be Closed Out[edit]
Lessons Learned Report[edit]
- PM may need to study from previous projects
Project Audit[edit]
- formal review of project progress and results
- did project achieve benefits as planned
- was work accomplished according to plan
