Sunteți pe pagina 1din 8

Project Details

SerialID

ProjectPhase

TemplateVersionNumber 3.30
Lessons Learned Database Template
Purpose 1. To capture the project lessons learned information from project teams during end-of-phase reviews, monthly
checkpoints and other project interactions.
2. The filled-in template could be uploaded into the lessons learned website using the upload functionality
provided in the lessons learned website.
Overview of the Lessons There are four worksheets in the lessons learned database template, namely:
Learned Database 1. Project_Detail: This worksheet captures the Project Serial ID and the Project Phase.
Template
2. Instructions: The purpose of this worksheet is to provide instructions about using the template. This
worksheet can only be edited by the blueprint support team.

3. Lessons_Learned: This worksheet is the actual template where the lessons learned data needs to be
captured. Certain sections of the template are locked and can only be edited by the Blueprint support team.

4. Reference_Data: This worksheet comprises of Categories and Sub Categories. This worksheet can only be
edited by the Blueprint support team.

General Instructions Version - Always download the latest version of the Lessons Learned Database Template from the Blueprint
Website before using the template.
Template - Do not modify the structure of the template, as the template is mapped to specific tables and
columns in the Lessons Learned Database and modifying the template could result in template upload failures
during uploads in lessons learned website.
SOP - Please go through the Lessons Learned SOP for further details on the standard operating procedures.

User Prompt - The template is designed to prompts the user about the next field that needs to be populated by
coloring the field Yellow
Error Messaging and Validation - Validations have been built into this template to prevent erroneous data from
being entered. In case the user misses out filling certain fields for a Lessons Learned, The immediate next field
will turn Yellow and the Text is crossed out.
The last field (Validation Field) in every row provides the details of all data entry errors.

The user should not upload the template into the Lessons learned website if the validation field shows errors. If
the template is uploaded into the Lessons Learned website without correcting the errors, the website will reject
the erroneous records.

Mandatory Fields - The Template contains both mandatory and optional fields. Mandatory fields are highlighted
in Blue and Optional fields in Grey. Error messages will appear in the Validation column if the mandatory fields
are not filled up. It is recommended that the project team captures as much information as possible for each
lesson learned.

Instructions for filling Lessons Project_Details Worksheet

Project Details
Field Name Instruction for filling
SerialID The unique serial ID assigned for the project from clarity needs to be provided in this field
ProjectPhase The phase in which the project is currently in needs to be filled in this field by picking the list of options provided
from the drop down lists.
TemplateVersionNumber The version number of the template is pre-filled in this field - the user will not be able modify to this field. The
user however needs to be aware of the version number that is the most recent that is available in the Blueprint
website and should ensure that the latest version is downloaded before use.

Instructions for filling Lessons_ Learned Worksheet


Lessons Learned
Field Name Instruction for filling
SNo This is a pre-filled column. There are totally 100 rows provided for entering each lessons learned. The user will
not be able to edit this field
LessonsType The Lessons Learned Type could be either a Pluses or a Delta. There are two options provided to user in the
(*Mandatory Field) drop down list for this field, namely: Pluses and Delta.
Pluses are positive events that were experienced during the project within the context of process, relationships,
and results.
Deltas are the negative events that were experienced during the project within the context of process,
relationships, and results

Title A brief title is assigned to each lessons learned in this field. Title is assigned for easy reference purposes.
(*Mandatory Field)
Category and Sub The user needs to submit the lessons learned by selecting the appropriate category and sub-category which is
Category applicable for the lessons learned provided:
(*Mandatory Field)
The following categories are available:
Stakeholders and End Users
Project Team
Process Standards and Tools
Scope
Project Management
Solution Implementation

* Please refer to the "Reference_Data" worksheet to get a list of the various sub-categories under each
category.
Role The role of the person who experienced the respective lessons learned information is captured in this field.
(*Mandatory Field)
Description A detailed description of the lessons learned is captured in this field.
(*Mandatory Field)
CostImpact The cost impact in dollars is captured in this field. The impact can be categorized into High, Medium or Low.
(*Mandatory Field) Low - < 10% impact on the phase cost
Medium - > 10% and < 20% impact on the phase cost
High - > 20% impact on the phase cost
No Impact - No impact on the phase cost

ScheduleImpactinDays The schedule impact in days is captured in this field. The impact can be categorized into High, Medium or Low.
(*Mandatory Field) Low - < 10% impact on the phase schedule
Medium - > 10% and < 20% impact on the phase schedule
High - > 20% impact on the phase schedule
No Impact - No impact on the phase schedule

ImpactDescription Brief description of the impact on the project should be mentioned


(*Mandatory Field)
Priority The user is required to set a priority for the lessons learned information. Three options are provided namely:
(*Mandatory Field) High, Medium and Low. Priority should be chosen based on the impact the lessons learned had on the project.
IsRecommended If the user is recommending that the specific lessons learned can be shared with other projects then choose
"Yes" else chooses "No".
ActionRequired If the lessons learned is a Delta, determine whether any steps need to be taken to address this delta lessons
learned. If yes, the user chooses the option "Yes" from the drop down list else s/he chooses "No".
If the lessons learned is a Plus, then this field is "NA - Not Applicable".
ActionDescription If the user had chosen "Yes" for the Action Required field then the user is required to provide a brief description
of the action expected from the Action owner.
Status For Deltas, the current status should be updated before uploading the template into the database. Once
uploaded, the status could be tracked to closure through the lessons learned website. The current status could
be chosen from a list provided in the drop down.
ActionOwner The project manager or the user who has been delegated by the project manager is the owner for the lessons
learned. His/Her name needs to be filled in this field.
ActionDueDate The due date by which the action is required to be completed is captured in this field.
Justification Justification needs to provided if Action Required column is marked as "NO" for a Delta lessons learned
SNo LessonsType Title Category SubCategory Role Description CostImpact ScheduleImpactinDays ImpactDescription Priority IsRecommended ActionRequired ActionDescription Status ActionOwner ActionDueDate Justification Validation

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67
68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94
Categories and Sub Categories
Stakeholders Project Team Process Standards Scope Project Management Solution
and End Users and Tools Implementation

Acceptance Composition Architectural Definition Integration Architecture


Standards (Bricks, Management
ICE, etc.)
Identification Involvement Blueprint Identification Time Management Functionality
Involvement Skills Capacity Planning Management Cost Management Infrastructure
Readiness Assignment Clarity Traceability Quality Management Networks
and allocation
Disaster Recovery Human Resource Rollout
Management
Governance Communications Security
Management
Project Specific Risk Management Training
Processes
Rational Tool Suite Procurement
Management
Security
SOX