Project Name

LESSONS LEARNED CHECKLIST TEMPLATE

Project Name:

Prepared by:

Document Revision/Release Status

Revision Date Description of Changes Author / Editor

0.0.1 MM/DD/YYYY Initial draft

Modify the text of this document to fit your project.

1. Project Lessons-Learned Checklist

No. Lesson Learned Yes No N/A Impact
Low High

1 2 3 4 5

Place your cursor in the appropriate boxes and type an X. (Insert additional rows as needed.)
Project Planning
1 Business Objectives were specific, measurable, attainable,
. results-focused and time-limited.

2 Product concept was appropriate to Business Objectives.

.

3 Project Plan and Schedule were well-documented, with

. appropriate structure and detail.

4 Project Schedule encompassed all aspects of the project.

.

5 Tasks were defined adequately.

.

Page 1 of 7
Lessons Learned Checklist Project Name

1. Project Lessons-Learned Checklist

No. Lesson Learned Yes No N/A Impact
Low High

1 2 3 4 5

6 Stakeholders (e.g., Sponsor, Customer) had appropriate

. input into the project planning process.

7 Requirements were gathered to sufficient detail.

.

8 Requirements were documented clearly.

.

9 Specifications were clear and well-documented..

.

1 Test Plan was adequate, understandable, and well-

0 documented.
.

1 External dependencies were identified, agreements signed.

1
.

1 Project budget was well defined.

2
.

1 End of Phase Criteria were clear for all project phases.

3
.

1 Project Plan had buy-in from the stakeholders.

4
.

1 Stakeholders had easy access to Project Plan and Schedule.

5
.

Project Execution and Delivery

1 Project stuck to its original goals.

6
.

Page 2 of 7
Lessons Learned Checklist Project Name

1. Project Lessons-Learned Checklist

No. Lesson Learned Yes No N/A Impact
Low High

1 2 3 4 5

1 Changes in direction that did occur were of manageable

7 frequency and magnitude.
.

1 Project baselines (Scope, Time, Cost, Quality) were well-

8 managed (e.g., changed through a formal Change Control
. Process).

1 Design changes were well-controlled.

9
.

2 Basic project management processes (e.g., Risk

0 Management, Issue Management) were adequate.
.

2 Project tracked progress against baselines and reported

1 accurate status.
.

2 Procurement (e.g., RFP, Contract with vendor) went

2 smoothly.
.

2 Contracted vendor provided acceptable deliverables of

3 appropriate quality, on time, and within budget.
.

2 Stakeholders were satisfied with the information they

4 received.
.

2 The project had adequate Quality Control.

5
.

2 Requirements – specifications – Test Plan were well-

6 managed (e.g., Requirements Management System was
. used).

Page 3 of 7
Lessons Learned Checklist Project Name

1. Project Lessons-Learned Checklist

No. Lesson Learned Yes No N/A Impact
Low High

1 2 3 4 5

2 Risks were manageable.

7
.

Human Factors
2 Project Manager reported to the appropriate part of the
8 organization.
.

2 Project Manager was effective.

9
.

3 Project Manager was not a contracted resource.

0
.

3 Project Team was properly organized and staffed.

1
.

3 Project Manager and staff received adequate training.

2
.

3 Project Team’s talent and experience were adequate.

3
.

3 Project team worked effectively on project goals.

4
.

3 Project team worked effectively with outside entities

5
.

3 There was good communication within the Project Team.

6
.

Page 4 of 7
Lessons Learned Checklist Project Name

1. Project Lessons-Learned Checklist

No. Lesson Learned Yes No N/A Impact
Low High

1 2 3 4 5

3 Management gave this project adequate attention and time.

7
.

3 Resources were not over-committed.

8
.

3 Resources were consistently committed to project aims.

9
.

4 Functional areas cooperated well.

0
.

4 Conflicting departmental goals did not cause problems.

1
.

4 Authority and accountability were well defined and public.

2
.

Overall
4 Initial cost and schedule estimates were accurate.
3
.

4 Product was delivered within amended schedule.

4
.

4 Product was delivered within amended budget.

5
.

4 Overall Change Control was effective.

6
.

Page 5 of 7
Lessons Learned Checklist Project Name

1. Project Lessons-Learned Checklist

No. Lesson Learned Yes No N/A Impact
Low High

1 2 3 4 5

4 External dependencies were understood and well-managed.

7
.

4 Technology chosen was appropriate.

8
.

4 The project was a technological success.

9
.

5 Customer’s needs/requirements were met.

0
.

5 Customer was satisfied with the product.

1
.

5 Project Objectives were met.

2
.

5 Business Objectives were met.

3
.

2. Project Lessons-Learned Checklist – Agreement Form / Signatures

Project Name:

Project
Manager:
I have reviewed the information contained in this Project Lessons-Learned Checklist and agree.

Name Title Signature Date

(MM/DD/YYYY)

Page 6 of 7
Lessons Learned Checklist Project Name

2. Project Lessons-Learned Checklist – Agreement Form / Signatures

The signatures above indicate an understanding of the purpose and content of this document by
those signing it. By signing this document, they agree to this as the formal Project Lessons-Learned
Checklist.

***End of Document***

Page 7 of 7