Project Name:

Module No.:

Project Team Lead:

LL# Lesson Type Event

The Lessons Log is a project repository used to record:

Lessons learnt from previous projects that are input to ‘this’ project, perhaps to help shape the projects strategies, plans a
team.

Lessons learnt from ‘this’ project that can be passed on and applied to other projects. Lessons recorded can be both good

A Lessons Learnt must capture : Success, Challenges and Difficulties, Shortcomings and Recommended Changes

Lessons Learned

Celebrate small wins / success

cater reporting to stakeholder needs

Tell management about the successes

Write a Project Management handbook

Provide monitoring and advisory services

Create PMO services across the spectrum

Create a lessons learned Database / Portal

Standardize - Methods, Processes, Tools, Techniques, Checklists,….

 LESSONS LOG

Number of Total Lessons:

Number of Lessons with early warnings:

Effect Causes / Trigger

perhaps to help shape the projects strategies, plans and shape the project management

o other projects. Lessons recorded can be both good and bad.

hortcomings and Recommended Changes

 LESSONS LOG

Criteria

No. of Priority 1: Priority 1: High - Project Stopper

No. of Priority 2: Priority 2: Medium

No. of Priority 3: Priority 3: Low

Previously
Early Warnings? Recommendations Date Logged
Identified?
iteria

Project Stopper

um

Focus Meeting Document

Logged By +/- Priority #
# access source
 Project Name:

Module No.:

Project Team Lead:

LL# Incident / Risk Lessons Learnt

Number of Total Lessons:

Action Item Owner Status

LL# Month Year Function Incident
1
MS Data loss in DPK server
Nov 2017 QA
due to HDD failed

4
sales team has escalated that
Jun 2017 Production used NBs was delivered to
them instead of brand new

Carton boxes / Buffers

Jun 2017 Warehouse
shortage for production

Customer complaint received

Apr 2017 QA on additional server HDD
screws missing

8 Jan 2017 Logistics Shipment thru AIR mode -

Earlier it was operated thru
single freight forwarder
[monopoly]

Customer feed-back on dust

Jan 2017 Production
found in note book

Support function has given a

10 feedback about the RDVD
Jan 2017 QA media, mismatch between the
chipset and the one available
in the media
 Lessons Learnt
Impact Team Lessons learned

Cycle time / cost Pondy QA Team No back-up mechanism

Unnecessary apprehension created in

HO OFG & identifying box seals between HQ direct
Customer order is affected
Thanga & Team imported note books & note books
produced by Pondy factory.

Space issue in warehouse to store the

carton / buffers as per the PO placed by
Productivity loss / Increased MOH Pondy WH Team
HO. Material planning need to be
revisited

Normally we will fix 2 x 2.5" HDD along

with each server. If the customer want to While assembling the system, we need
upgrade their system, they may add the HDD Pondy QA Team to consider the future upgradation points
for which they require additional HDD screws also from the customer perspective
and may not available in the local market

Delay in customer delivery due to fixed space Corporate Issues in meeting customer time line
capacity in the airline for month end Logistics deliveries
shipments & freight charges were on the
higher side

Existing production floor set-up is not

Field issues / customer dissatisfaction Thanga & Team enough for dust free environment to
produce note book & touch products

Person dependent / expensive / huge HO Planning Team Single part code used for various MBD
inventory & Pondy QA Team drivers
essons Learnt
Source Result Controls Implemented Date

Server created with dual HDD [Raid 1] so

Internal Successful On-going
that back up is created and data preserved.

Product seal is standardized as there is no

difference in HQ & Pondy factory so that
Internal Successful 30.06.17
customer will not have any ambiguity
between two different seals

We have advised carton / buffer vendors to

produce the materials against PO and
External Successful supply as per our daily schedule so that we 05.07.17
will have sufficient space to store the
packing materials for day production

While doing assembly of such export

servers, we need to additionally provide
Internal Successful 30.04.17
HDD screws for future upgradation as a
part of system accessory

External Successful Alternate service provider M/s. Spicejet 30.01.17

inducted and options available for multiple
space for air connectivity with lesser
freight charges

One more production line been created

with minimum entry points & with
Internal Successful complete dust free environment to cater 25.01.17
the manufacturing of note books / touch
products

Created individual part codes for various

Internal Successful MBD drivers so that there will not be any 02.02.17
ambiguity while assembly
Document access source One point lesson# if applicable Remarks
\\10.118.4.4\Audit\ISO9001\LL
N/A

\\10.118.4.4\Audit\ISO9001\LL

OPL # 2

\\10.118.4.4\Audit\ISO9001\LL

N/A

\\10.118.4.4\Audit\ISO9001\LL

N/A

\\10.118.4.4\Audit\ISO9001\LL N/A

\\10.118.4.4\Audit\ISO9001\LL

N/A

\\10.118.4.4\Audit\ISO9001\LL
OPL # 1