professional documents
home
Profile
docsters
request
Blogs
Upload
about me
contact me
user photo
submit clear
Word Document

Lessons Learned Checklist Template center doc

Project Name Page 1 of 4 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. 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.. Lessons Learned Checklist Project Name Page 2 of 4 1. Project Lessons-Learned Checklist No. Lesson Learned Yes No N/A Impact Low High 1 2 3 4 5 10. Test Plan was adequate, understandable, and welldocummented 11. External dependencies were identified, agreements signed. 12. Project budget was well defined. 13. End of Phase Criteria were clear for all project phases. 14. Project Plan had buy-in from the stakeholders. 15. Stakeholders had easy access to Project Plan and Schedule. Project Execution and Delivery 16. Project stuck to its original goals. 17. Changes in direction that did occur were of manageable frequency and magnitude. 18. Project baselines (Scope, Time, Cost, Quality) were wellmannage (e.g., changed through a formal Change Control Process). 19. Design changes were well-controlled. 20. Basic project management processes (e.g., Risk Management, Issue Management) were adequate. 21. Project tracked progress against baselines and reported accurate status. 22. Procurement (e.g., RFP, Contract with vendor) went smoothly. 23. Contracted vendor provided acceptable deliverables of appropriate quality, on time, and within budget. 24. Stakeholders were satisfied with the information they received. 25. The project had adequate Quality Control. 26. Requirements – specifications – Test Plan were wellmannage (e.g., Requirements Management System was used). 27. Risks were manageable. Human Factors 28. Project Manager reported to the appropriate part of the organization. 29. Project Manager was effective. Lessons Learned Checklist Project Name Page 3 of 4 1. Project Lessons-Learned Checklist No. Lesson Learned Yes No N/A Impact Low High 1 2 3 4 5 30. Project Manager was not a contracted resource. 31. Project Team was properly organized and staffed. 32. Project Manager and staff received adequate training. 33. Project Team’s talent and experience were adequate. 34. Project team worked effectively on project goals. 35. Project team worked effectively with outside entities 36. There was good communication within the Project Team. 37. Management gave this project adequate attention and time. 38. Resources were not over-committed. 39. Resources were consistently committed to project aims. 40. Functional areas cooperated well. 41. Conflicting departmental goals did not cause problems. 42. Authority and accountability were well defined and public. Overall 43. Initial cost and schedule estimates were accurate. 44. Product was delivered within amended schedule. 45. Product was delivered within amended budget. 46. Overall Change Control was effective. 47. External dependencies were understood and well-managed. 48. Technology chosen was appropriate. 49. The project was a technological success. 50. Customer’s needs/requirements were met. 51. Customer was satisfied with the product. 52. Project Objectives were met. 53. Business Objectives were met. Lessons Learned Checklist Project Name Page 4 of 4 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) 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***
rate this doc
email this doc
embed this doc
add to folder
digg reddit stumble delicious
flag this doc
831
143
8(1)
1
1/6/2008
English
search termpage on Googletimes searched
Preview

Lessons Learned Template

destined 1/4/2008 | 2224 | 277 | 1 | business
Preview

Lessons_Learned_Checklist_Template

patreciaw 2/19/2008 | 330 | 59 | 0 | business
Preview

Lessons Learned Template (Joint-JULLS format)

makatak 3/11/2008 | 469 | 38 | 0 | technology
Preview

Lessons Learned Checklist Template[1]

ocak 1/10/2008 | 285 | 77 | 0 | business
Preview

Lessons Learned Document Template[1]

ocak 1/10/2008 | 370 | 74 | 0 | business
Preview

Lesseons Learned Document Template

ocak 1/10/2008 | 235 | 21 | 0 | business
Preview

lessons learned document template

ocak 1/6/2008 | 576 | 45 | 0 | business
Preview

Lessons_Learned_Document_Template

ocak 1/6/2008 | 247 | 30 | 0 | business
Preview

Lesson Learned Document Template English

ocak 1/6/2008 | 250 | 17 | 0 | business
Preview

The PMP Exam - My Lesson Learned

csoliveira 5/15/2008 | 1859 | 168 | 0 | educational
Preview

Template Project Scale[1]

ocak 1/28/2008 | 1191 | 1507 | 2 | business
Preview

Strategic Asset Plans[1]

ocak 1/28/2008 | 713 | 252 | 2 | business
Preview

Steering Committee Charter template[1]

ocak 1/28/2008 | 1369 | 310 | 3 | business
Preview

Status Report Management Process Flow example[1]

ocak 1/28/2008 | 1513 | 502 | 1 | business
Preview

Status Report example[1]

ocak 1/28/2008 | 1663 | 651 | 2 | business
Preview

Software Requirement Specifications Document Template[1]

ocak 1/28/2008 | 1247 | 246 | 1 | business
Preview

Scope Statement Development Instructions[1]

ocak 1/28/2008 | 507 | 32 | 0 | business
Preview

Schedule Of Excess Risks[1]

ocak 1/28/2008 | 261 | 18 | 0 | business
Preview

Sample Performance Based Requirement Template for use with Task Orders[1]

ocak 1/28/2008 | 382 | 21 | 0 | business
Preview

Risk Value Assessment Tool

ocak 1/28/2008 | 433 | 56 | 1 | business
 
review this doc
Great-looking document - very useful
Rated 8 out of 10

March 11, 2008 (3 months 24 days ago)This is a good template for project management lessons learned. Already has an extensive list of project management measures. Nice work!