This preview shows page 1. Sign up to view the full content.
Unformatted text preview: project completion. Each phase of the project should be properly closed to ensure that important and useful information is not lost. In addition, employee skills in the staff pool database should be updated to reflect new skills and proficiency increases. .1 Performance measurement documentation .2 Product documentation .3 Other project records A Guide to the A Guide to the
.1 Performance reporting tools and techniques .2 Project reports .3 Project presentations Inputs Tools & Techniques Outputs
.1 Project archives .2 Project closure .3 Lessons learned 10.4.1 Inputs to Administrative Closure .1 Performance measurement documentation. All documentation produced to record and analyze project performance, including the planning documents that established the framework for performance measurement, must be available for review during administrative closure. .2 Product documentation. Documents produced to describe the product of the project (plans, specifications, technical documentation, drawings, electronic files, etc.--the terminology varies by application area) must also be available for review during administrative closure. .3 Other project records. Project records are discussed in Section 10.2.3.1. Project Project Management Management Body of Body of KnowledgeE L KnowledgeE PL MP AM SA S 10.4.2 Tools and Techniques for Administrative Closure .1 Performance reporting tools and techniques. Performance reporting tools and techniques are discussed in Section 10.3.2. .2 Project reports. See Section 10.2.3.2. .3 Project presentations. See Section 10.2.3.3. 10.4.3 Outputs from Administrative Closure .1 Project archives. A complete set of indexed project records should be prepared for archiving by the appropriate parties. Any project-specific or programwide historical databases pertinent to the project should be updated. When projects are done under contract, or when they involve significant procurement, particular attention must be paid to archiving of financial records. A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 Edition 2000 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA NAVIGATION LINKS ACROYMNS LIST ACRONYMS LIST 125 ACROYMNS LIST Chapter 10--Project Communications Management 10.4.3.2 | Chapter 11 .2 Project closure. Confirmation that the project has met all customer requirements for the product of the project (the customer has formally accepted the project results and deliverables and the requirements of the delivering organization--for example, staff evaluations, budget reports, lessons learned, etc.). .3 Lessons learned. Lessons learned are discussed in Section 220.127.116.11. ment ment geE L geE PL P 126 NAVIGATION LINKS ACROYMNS LIST ACRONYMS LIST ACROYMNS LIST A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 Edition 2000 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA Chapter 11 Project Risk Management
A Guide to the A Gu...
View Full Document
This document was uploaded on 09/27/2013.
- Fall '13
- The American