Page 130 -

4 - PROJECT INTEGRATION MANAGEMENT

• Project files—Documentation resulting from the project’s activities, for example, project management
plan; scope, cost, schedule, and project calendars; risk registers and other registers; change management
documentation; planned risk response actions; and risk impact.
• Project or phase closure documents—Project or phase closure documents, consisting of formal
documentation that indicates completion of the project or phase and the transfer of the completed
project or phase deliverables to others, such as an operations group or to the next phase. During project
closure, the project manager reviews prior phase documentation, customer acceptance documentation
from the Validate Scope process (Section 5.4), and the contract (if applicable), to ensure that all project
requirements are completed prior to finalizing the closure of the project. If the project was terminated
prior to completion, the formal documentation indicates why the project was terminated and formalizes
the procedures for the transfer of the finished and unfinished deliverables of the cancelled project to
others.
• Historical information—Historical information and lessons learned information are transferred to the
lessons learned knowledge base for use by future projects or phases. This can include information on
issues and risks as well as techniques that worked well that can be applied to future projects.

104 ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.