Page 84 -

3 - PROJECT MANAGEMENT PROCESSES

This Process Group also formally establishes the premature closure of the project. Prematurely closed projects
may include, for example: aborted projects, cancelled projects, and projects having a critical situation. In specific
cases, when some contracts cannot be formally closed (e.g. claims, termination clauses, etc.) or some activities
are to be transferred to other organizational units, specific hand-over procedures may be arranged and finalized.

At project or phase closure, the following may occur:
• Obtain acceptance by the customer or sponsor to formally close the project or phase,

• Conduct post-project or phase-end review,
• Record impacts of tailoring to any process,

• Document lessons learned,
• Apply appropriate updates to organizational process assets,
• Archive all relevant project documents in the project management information system (PMIS) to be used
as historical data,

• Close out all procurement activities ensuring termination of all relevant agreements, and
• Perform team members’ assessments and release project resources.

3.8 Project Information

Throughout the life cycle of the project, a significant amount of data and information is collected, analyzed,
transformed, and distributed in various formats to project team members and other stakeholders. Project data are
collected as a result of various Executing processes and are shared within the project team. The collected data
are analyzed in context, and aggregated and transformed to become project information during various Controlling
processes. The information may then be communicated verbally or stored and distributed as reports in various
formats.

The project data are continuously collected and analyzed during the dynamic context of the project execution.
As a result, the terms data and information are often used interchangeably in practice. The indiscriminate use
of these terms can lead to confusion and misunderstandings by the various project stakeholders. The following
guidelines help minimize miscommunication and help the project team use appropriate terminology:

58 ©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.