KOHASA ENGINEERING COMPANY LIMITED

Documented Information Title: PROJECT LESSONS-LEARNED

PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 01 Page 1 of 11

APPROVAL AND REVISION STATUS

Rev. Issue Date Revision Prepared Reviewed by Approved

No. Identificati By by
on
First Engineering Technical
02 21st Apr, 2022 PCON Head
Revision Manager Director
E.G.T N.U.E S.M.K
Initials, Signature, And Date
21/04/2021 21/04/2021 21/04/2021
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 2 of 11

CHANGES/REVISION HISTORY TABLE

The change(s)/amendment(s) noted below have been made, reviewed and approved by the
involved parties for issue

Name Job Title Dept/Unit Sign Date

Nicholas Emmana Umoh Engineering Manager Engineering 21/04/2022

Revision Page(s)/ Proposed Reviewed

Date of Issue Reason for changes Section(s) Approved By
No. By By
Affected

Entire Nicholas
Updating Document Sadiq Musa Eduard
1 13/01/2020 document Umoh
Kida Koumako

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 3 of 11

Table of Contents

1. INTRODUCTION ...................................................................................... 4
2. PURPOSE OF DOCUMENT ........................................................................... 4
3. OBJECTIVE ........................................................................................... 4
4. REFERENCES ......................................................................................... 5
5. TERMS AND DEFINITIONS ........................................................................... 5
6. ABBREVIATIONS AND MEANING .................................................................... 6
7. RESPONSIBILITIES AND AUTHORITY............................................................... 7
7.1 Project Manager ............................................................................. 7
7.2 Project Engineer ............................................................................. 7
7.3 Project Control Engineer ................................................................... 7
7.4 Document Control Officer .................................................................. 7
7.5 Responsible Persons ......................................................................... 7
8. PROCEDURE.......................................................................................... 7
8.1 Lessons Learned ............................................................................. 7
8.2 Lessons Learned applied from previous Projects ....................................... 8
8.3 Process Improvement Recommendations ................................................ 8
8.4 Time to Start the Processes................................................................ 8
8.5 Project Progress Meeting ................................................................... 9
8.6 Project Closeout Meeting / Discussion .................................................. 10
9. RECORDS ............................................................................................ 10

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 4 of 11

1. INTRODUCTION

Capturing lessons learned is an integral part of every project and serves several purposes.
While the finalization of a formal lessons learned document is completed during the project
closeout process, capturing lessons learned should occur throughout the project lifecycle to
ensure all information is documented in a timely and accurate manner. The lessons learned
document serves as a valuable tool for use by other project managers within KOHASA as an
organization who are assigned similar projects. This document should not only describe what
went wrong during a project and suggestions to avoid similar occurrences in the future, but it
should also describe what went well and how similar projects may benefit from this
information. This document shall be communicated to the entire Project Team for every
project.

2. PURPOSE OF DOCUMENT

The purpose of this document is to help the project team share knowledge gained from the
project so that the entire organization may benefit. A successful Lessons-Learned program
will help project teams:

 Repeat desirable outcomes

 Avoid undesirable outcomes.

3. OBJECTIVE

 Each project captures all its Lessons Learned before the end of the project
 All Lessons Learned are properly documented
 All Lessons Learned are reviewed, categorized and grouped as appropriate by the Project
Team
 All Lessons Learned are available for general viewing throughout the organization

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 5 of 11

4. REFERENCES

 ISO 9001:2015, Quality Management Systems

 Engineering Design and Development Procedure

5. TERMS AND DEFINITIONS

A COMPANY that engages the Professional Engineering

Services of KOHASA, with a financial obligation to adopt the
CLIENT
services, advice, representation of KOHASA, and receive
confidentiality in return and safe delivery of a qualitative service.
A CONTRACTOR (Kohasa Engineering Company Limited)
rendering Engineering Design, Project Management, and
KOHASA
Construction services in the oil and gas and other relevant
production industries.
Approved technical and logistic systems to support the primary
and secondary systems, which must be developed in an
ENGINEERING
integrated manner due to the interactions that exist between
them and with the above-mentioned systems.
A structured set of data held in a computer, especially one that
DATABASE
is accessible in various ways
A collaborative enterprise entrusted to KOHASA planned and
PROJECT designed to achieve a concrete aim commensurate with that of
the CLIENT.
Lessons learned or lessons learned are experiences distilled
LESSONS LEARNED from a project that should be actively taken into account in
future projects.
STRATEGIES A plan of action designed to achieve a long-term or overall aim
POTENTIAL Having or showing the capacity to develop into something in the
IMPROVEMENT future, increased value or excellence
Set of interrelated or interacting activities that transform inputs
PROCESSES
into outputs.

SUCCESS The accomplishment of an aim or purpose.

PROJECT CLOSE-OUT Is the last phase of the project management lifecycle

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 6 of 11

6. ABBREVIATIONS AND MEANING

KECL KOHASA Engineering Company Limited

EM Engineering Manager
PM Project Manager
PE Project Engineer
PCON Project Control
DB Database
LL Lessons Learned
LLL Lessons Learned Log
DCC Document Control Centre
DC Document Control
TD Technical Director
OPD Operations Director

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 7 of 11

7. RESPONSIBILITIES AND AUTHORITY

7.1 Project Manager

 The Project Manager has the responsibilities of initiating/driving the lessons learned
processes

7.2 Project Engineer

 The Project Engineer is vested with the responsibilities of collation of data,
documentation and assisting the Project Manager

7.3 Project Control Engineer

 The Project Control Engineer has the responsibilities of monitoring the process

7.4 Document Control Officer

 The Document Control Officer has the responsibilities of documenting lessons learned
meeting outcomes

7.5 Responsible Persons

 Project Managers
 Project Engineers

8. PROCEDURE

8.1 Lessons Learned

The lessons learned must be communicated consistently (During project kick-off and progress

meetings). In addition to the categorization and description of the lesson, it is important to

state what the impact was and provide a recommendation for project managers to consider on

future projects. It is important to note that not only failures or shortcomings are included but

successes as well.

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 8 of 11

8.2 Lessons Learned applied from previous Projects

The lessons learned document for the previous project are sighted during a new project

internal / progress meetings, to serve as a guide. This information not only shows the value of

the documentation of such lessons, but it also shows which lessons are consistently applied

by other similar projects. It is important to reference not only what the lesson was but from

which project it was associated with.

8.3 Process Improvement Recommendations

It is important that once lessons learned are collected and documented, The project manager,

shall approve and implement any process improvements identified. Organizations need to

strive for continuous improvement and this portion of the lessons learned process is an

integral step.

8.4 Time to Start the Processes

The Project Manager will introduce all that is needed to drive this process from the internal

Project kicks off meeting and the Project team should begin to use this document at its first

project progress meeting. Continually recording Lessons-Learned throughout the project is the

best way to ensure that they are accurately recorded. Topics can be selected from the

following;

Note: Project team is not bid by these topics. It is just a guide.

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 9 of 11

Project Management Technical Management Human Factors Overall

 Project Planning  Requirements  Communication  Customer Satisfaction

 Resource Management  Specification  Team Experience  Technical Success

 Risk Management  Test Plan  Interaction with  Quality product

Sponsor

 Change Control  Construction  Interaction with  Product Accepted

Customer

 Procurement  Testing  Interaction with  On-Time

Management

 Budget Management  Rollout  Management  Within Budget

support

 Quality Control  Training  Quality of meetings  Met Project

Objectives

 Status Reports  Documentation  Vendor interaction  Met Business

Objectives

 Vendor Selection  Vendor Management

8.5 Project Progress Meeting

Every last week of the month during the internal project progress meeting, the Project team is
to discuss what strategies contributed to success as well as areas of potential improvement
and enter conclusions in the Lessons Learned Log.

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 10 of
11

8.6 Project Closeout Meeting / Discussion

The Project management team will gather all Lessons-Learned and conduct meetings for
project closeout at the end of the project, and this should happen not later than 4 weeks and
not earlier than 3 weeks after the project closeout report is submitted.
During the team discussions: the following shall be followed

 Be positive
 Do not place blame!
 Focus on successes as well as failures
 Indicate which strategies contributed to the success
 Indicate which improvement strategies would have the greatest impact

9. RECORDS

 PROJECT LESSONS LEARNED LOG

 ATTENDANCE SHEET

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED
 KOHASA ENGINEERING COMPANY LIMITED
Documented Information Title: PROJECT LESSONS-LEARNED
PROCEDURE

Ref. No: KECL/ENG/PRC/1110 Issue Date: 21st Apr, 2022 Rev. No.: 02 Page 11 of
11

APPENDIX A – LESSONS LEARNED LOG

Project Lessons
Learned LOG.xlsx

All rights reserved. None of the information contained in this document shall be disclosed outside own company, and no part of this
document may be reproduced or transmitted without the written permission of KOHASA ENGINEERING COMPANY LIMITED