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

Lessons Learned Checklist Template[1] center doc

Put your logo here Put your organization name here Project Lessons-Learned Checklist Template Rev. 1.0, 12/07/2003 Page 1 of 3 PROJECT LESSONS-LEARNED CHECKLIST Project Name: Prepared by: Date (MM/DD/YYYY): 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 10. Test Plan was adequate, understandable, and welldocummente 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 Put your logo here Put your organization name here Project Lessons-Learned Checklist Template Rev. 1.0, 12/07/2003 Page 2 of 3 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.) 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 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 Put your logo here Put your organization name here Project Lessons-Learned Checklist Template Rev. 1.0, 12/07/2003 Page 3 of 3 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.) 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 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.
rate this doc
email this doc
embed this doc
add to folder
digg reddit stumble delicious
flag this doc
355
88
not rated
0
1/10/2008
English
search termpage on Googletimes searched
Preview

Lessons Learned Checklist Template

ocak 1/6/2008 | 1004 | 177 | 1 | business
Preview

Lessons Learned Document Template[1]

ocak 1/10/2008 | 456 | 87 | 0 | business
Preview

Lessons Learned Template

destined 1/4/2008 | 2463 | 320 | 1 | business
Preview

Lesseons Learned Document Template

ocak 1/10/2008 | 270 | 28 | 0 | business
Preview

Project Budget Template[1]

ocak 1/10/2008 | 540 | 152 | 0 | business
Preview

Risk Management Plan Template[1]

ocak 1/10/2008 | 945 | 121 | 0 | business
Preview

Project Management Summary Template

ocak 1/10/2008 | 773 | 141 | 0 | business
Preview

Project Management Template Index

ocak 1/10/2008 | 1514 | 254 | 1 | business
Preview

Lessons_Learned_Document_Template

ocak 1/6/2008 | 269 | 35 | 0 | business
Preview

lessons learned document template

ocak 1/6/2008 | 705 | 55 | 0 | business
Preview

Issue Log Template[1]

ocak 1/10/2008 | 619 | 94 | 0 | business
Preview

Procurement Plan Template[1]

ocak 1/10/2008 | 207 | 28 | 0 | business
Preview

Requirements Document Template[1]

ocak 1/10/2008 | 563 | 76 | 0 | business
Preview

Scope Statement Template[1]

ocak 1/10/2008 | 961 | 155 | 1 | business
Preview

Meeting Minutes Template[1]

ocak 1/10/2008 | 743 | 112 | 1 | business
Preview

Template Project Scale[1]

ocak 1/28/2008 | 1412 | 1547 | 2 |
Preview

Strategic Asset Plans[1]

ocak 1/28/2008 | 828 | 296 | 2 | business
Preview

Steering Committee Charter template[1]

ocak 1/28/2008 | 1638 | 352 | 3 | business
Preview

Status Report Management Process Flow example[1]

ocak 1/28/2008 | 1721 | 563 | 1 | business
Preview

Status Report example[1]

ocak 1/28/2008 | 1955 | 735 | 2 | business
Preview

Software Requirement Specifications Document Template[1]

ocak 1/28/2008 | 1541 | 275 | 1 | business
Preview

Scope Statement Development Instructions[1]

ocak 1/28/2008 | 578 | 35 | 0 | business
Preview

Schedule Of Excess Risks[1]

ocak 1/28/2008 | 300 | 19 | 0 | business
Preview

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

ocak 1/28/2008 | 500 | 22 | 0 | business
Preview

Risk Value Assessment Tool

ocak 1/28/2008 | 511 | 69 | 1 | business
"checklist template"11
"lessons learned checklist"11
lessons learned checklist download11
 
review this doc