DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
LESSONS LEARNED DOCUMENT FOR
<PROJECT NAME>
AUTHOR:
CLIENT:
RELEASE DATE:
BUSINESS SPONSOR:
PAGE 1 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
TABLE OF CONTENTS
PART 1: VERSION HISTORY...................................................................................................................................3
PART 2: APPROVALS AND SIGN-OFF..................................................................................................................4
PART 3: KEY RESOURCES AND DOCUMENT CIRCULATION......................................................................5
PART 4: EXECUTIVE SUMMARY..........................................................................................................................6
SECTION 1 : BACKGROUND........................................................................................................................................6
SECTION 2 : OBJECTIVES OF THE PROJECT.............................................................................................................6
SECTION 3 : BENEFITS FROM THE PROJECT............................................................................................................6
SECTION 4 : CMT ROLES..........................................................................................................................................6
SECTION 5: SCOPE OF REPORT................................................................................................................................6
PART 5 : PROJECT REVIEW...................................................................................................................................7
SECTION 1 : PROJECT GOVERNANCE & PROJECT CONTROLS...............................................................................7
SECTION 2: TOOLS.....................................................................................................................................................7
PART 6: MEASUREMENTS REVIEW.....................................................................................................................8
PART 7: SIGNIFICANT LESSONS...........................................................................................................................9
PAGE 2 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
PART 1: VERSION HISTORY
Version Author Date Comments
PAGE 3 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
PART 2: APPROVALS AND SIGN-OFF
This document has been approved as the vision and scope report for the project and accurately reflects the current
understanding of the proposed solution, its scope and associated risks. Following approval of this document,
requirement changes will be governed by the project’s change management process, including impact analysis,
appropriate reviews, and approvals under the general control of the project plan and according to company policy.
Prepared by
NAME Date
Approved by
NAME Date
PAGE 4 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
PART 3: KEY RESOURCES AND DOCUMENT CIRCULATION
# Department Name
1 CMT India
PAGE 5 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
PART 4: EXECUTIVE SUMMARY
Section 1 : Background
Section 2 : Objectives of the Project
Section 3 : Benefits from the Project
Section 4 : CMT Roles
Section 5: Scope of Report
PAGE 6 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
PART 5 : PROJECT REVIEW
Section 1 : Project Governance & Project Controls
<Describe key project control methods followed>
Section 2: Tools
<Describe tools enabling business analysis used in the project>
PAGE 7 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
PART 6: MEASUREMENTS REVIEW
<Describe review processes followed in the project for ensuring project conformance and requirements traceability>
PAGE 8 OF 9
DOCUMENT NAME VERSION:
PROJECT NAME: DATE:
PART 7: SIGNIFICANT LESSONS
[Link]. Issue/Learnings Mitigation Action
A. Background
Data flow analysis project was implemented to map data dependencies for all finance groups
and bring transparency in data flows from source system to time it reaches the user
B. Objectives of the project were to:
Document and analyse existing business processes & data flows
Identify and suggest areas of improvement for reducing the turnaround time of system delivered
data
C. Benefits from the project:
The Project improved the visibility of FINANCE IT system flows and business process flows for
the business users. It helped in better understanding of the handoffs, time of delivery of data and
SLAs.
The project allowed to question the status quo and assisted in improving the processes.
Product Control: Out of 111 P&Ls analysed - 49 P&Ls being delivered ~3 hours, 5 P&Ls being
delivered ~4 hours and 10 P&Ls being delivered ~1.5 hours earlier daily.
Treasury: Box reports and NBI MCO being generated ~1 hour early daily.
Financial Planning and Strategy: Generation of 300+ sales reports being improved by ~1 hour
Documented and increased data transparency for 158 process group of finance division
PAGE 9 OF 9
