3 CLOSING REPORT OF

PROJECT
2
General Instructions:

The Closure Report is a document that summarizes the most relevant aspects of the project in
regarding the results obtained and the overall performance of the project, in relation to what was planned.

1. TECHNICAL PERFORMANCE:
a. What would be the result of comparing the final scope of the work with its initial scope?
of the project?
Did the project scope register many changes?
c. Were the changes managed correctly in terms of documentation, authorizations and
communication?
d. What effect did the changes in the budget and the project program have?
e. Was the scope of work completely finished?
f. The project work and deliverables were completed with good quality and met the
customer expectations?

2. BUDGET PERFORMANCE:
a. What would be the result of comparing the actual costs of the project with the
original basic budget and with the final budget of the project, which included the
changes in the scope of the project?
b. If there was a fixed price contract, was it profitable or did the project organization incur a loss?
money?
c. If there was a cost reimbursement contract, was the project completed within the
customer's budget?
d. Were there specific work packages that went over or fell below their budgets?
for more than 10%? In that case, why? What were the causes that led to it?
Will the costs overflow?
e. Were the estimated costs for the activities realistic?

3. SCHEDULE PERFORMANCE:
a. What would be the result of comparing the actual program with the original program?
project?
b. If the project was delayed, what were the causes?
c. How did the program performance adjust to each work package?
d. Was the duration of the estimated times for the activities realistic?

4. PLANNING AND CONTROL OF THE PROJECT:

a. Was the project planned in sufficient detail?
b. Were the plans updated in a timely manner to incorporate the changes?
c. Was the actual performance compared to the planned one regularly?
d. Were the actual performance data correct and collected in a timely manner?
Did the project team use the planning and control system regularly? Did they use it?
for decision-making?

5. RISK MANAGEMENT:

7
 a. Did the presence of unexpected events affect the outcome of the project? If so, did the
Were the facts identified in the risk plan?
b. The risks that had a high probability of occurring and enormous impact were
properly identified at the beginning of the project?
c. Was there any risk that should have been identified at the start of the project, but wasn't?
d. What risks were identified during the project that had not been considered before
principle and why were they not identified then?
e. In the case of the identified risks that were presented, were the response plans
adequate?
f. Were there unexpected events for which there were no response plans?

6. CUSTOMER RELATIONS:
a. Was everything necessary done for the client to participate in the success of the project?
b. Was the client regularly asked to express their level of satisfaction with the
performance and progress of the project?
c. Were regular face-to-face meetings with the client scheduled?
d. Was the client informed of the potential problems in a timely manner and asked to
Will you participate in the process to resolve them?

7. RELATIONSHIPS IN THE TEAM:

a. Did the team participate in the project planning?
b. Was there a sense of 'team' and a commitment to the success of the project?
c. Were there conditions that prevented teamwork?

8. COMMUNICATIONS:
a. Was the team kept informed about the project's status and issues?
potentially in advance?
b. Did the project environment facilitate open, honest, and timely communication?
c. Were the project meetings productive?
d. Were written communications within the team and with the client sufficient?
insufficient or excessive?

9. IDENTIFICATION AND SOLUTION OF PROBLEMS:

a. Were there mechanisms for team members to identify the problems?
potential in sufficient advance?
b. Did the indicated team members participate in problem-solving?
c. Was the problem-solving rational and thorough?

10. LESSONS LEARNED (see Annex 1):

a. What worked and what didn't work?
b. What particular things were done well in the project that contributed to its development and what
should it be done in other projects?
c. What things were done that hindered the development of the project and should be eliminated or
change in future projects?
d. If it were possible to start over and repeat the project, what should be done differently?
way?

11. RECOMMENDATIONS:
a. Based on the discussion and evaluation of the previous points conducted by the team,
What specific recommendations could be made to improve performance in
future projects?

VERSION CONTROL
Version Revised Response Approved Date Reason
ble For: By:

7
1.0
…

7
 ANNEX 1: LESSONS LEARNED

Actions
No. of Impact Description
Code of Name of Area / Close Threat Títul Descripción de Corrective and Lesson Learned
Reference in the objectives of
Project Project Category a Opportunity o the Situation Preventive Recomendaciones
a project
Implemented

INSTRUCTION:

Columna Instrucciones

7
Reference No. Numbering of the lesson learned according to the agreed format, identifies
unequivocally to a lesson learned.
Project Code The project code in which the lesson learned was identified.
Project Name Descriptive name of the project in which the lesson learned was identified.
Area / Category Categories in which lessons learned will be classified, for example, in
a Software Development project can be Technical, Functional,
Communication, Management of those involved, among others; or for example they could
use the areas of knowledge of Project Management, for example
scope, time, quality, communications, among others.
Date Day, month and year when the described situation occurred.
Threat / Opportunity It is indicated if the lesson learned is related to an adverse effect
(threat) that must be avoided in the future or is associated with an effect
positive in the project (opportunity) on which actions must be taken
to keep it.
Title Alluding to the situation presented.
Description of the Describe the background and circumstances that led to the subject matter.
Situation from the lesson learned, it is important to identify the root causes that
caused the situation.
Impact Description Effect that the proposed situation had on the project's objectives, due to
in the objectives of example: Delay in the project delivery date (expressed in unit of
project time), increase in costs (expressed in units of effort),
reduction of quality levels, customer dissatisfaction, among others. Also
It can reflect positive impacts, for example, the activity was finished early.
from the planned date, an activity was carried out at a fraction of the cost, between
others. It is important to express the impact in measurable terms.
Corrective Actions and List the corrective actions implemented to reduce or improve the
Preventive effects of the situation (depending on whether they are threats or opportunities) and
Implemented preventive actions to reduce or increase the probability that it
they will be presented again in the future.
Lesson Learned Summarize the actions and strategies to be adopted in the future to prevent that from happening.
Recommendations presents the threat again or to take advantage of the opportunity (if it is a
lesson of positive impact). It is built from experiences of the
actions taken to correct the situation.

EXAMPLE:

7
 Description Actions
Lesson
No. of Threat of the Impact Corrective and
Code of Name of the Area / Description of the Learned
Reference Date Opportunity Title in the Preventive measures
Project Project Category Situation Recommendation
a ad objectives of Implemented
is
project
XXXX- XXXX-XXXX- Development of Management of 28/10/201 Threat Document of Certain It was delayed. As action Implement a
XXXX-XX XX System for Requirement 1 Design with scenarios no date of corrective, it control of
Management of os insufficient were described delivery and itself
they carried out approval of
Lessons detail. in detail in the they incurred in the documents
meetings with
learned documents costs functional.
functional, in additional the users
your place, in for rework. to describe Include in the
some cases are the checklist of
made reference to the behavior approval that
behavior the expected and it the document
of a system updated the describe in
anterior. detail the
document of
processes of
This situation design business and
caused functional. behavior
interpretations Then it or expected.
inadequate of they carried out
reach by developments of
of the team of the functionality
development, for the
expected.
that certain
components no
were accepted As action
by the user preventive, if
final. they reviewed the
rest of the
documents of
design
functional for
search
identify
situations
similar and
take the
correctives
before
start to
develop those
components.