40 likes | 130 Views
Process for Gathering and Reporting Lessons Learned.
E N D
Process for Gathering and Reporting Lessons Learned The following pages were provided by a large COTS user and reflect their process for gathering lessons learned. Key point to note is that ‘lessons learned’ are gathered during the implementation vs. after – in this way immediate action can be taken in order to improve the implementation process. EITK0604
Lessons Learned – Background • At end of project = lessons observed • During project = lessons learned • Barriers • 40% PMs (NASA) believe there is too little time to spend on LL and are reluctant to share failures with others – might reflect poorly on PM performance • Hard to retrieve the right lesson at the right time • Not enough emphasis on positive or successful experiences
Lessons Learned – Process • At planning and at the end/start of major phases, each project conducts a focused review of lessons learned. This review will • Identify new lessons learned from team members • Review existing lessons in the Lessons Learned Database • Determine applicability of lessons to upcoming work • SQA and Methodologists will verify these reviews and facilitate the use of lessons learned • Summary reports of lessons learned, communication, and publications quarterly
Lessons Learned – Collection and Reporting • Project Reporting • Lessons Learned • Date of last review: • Summary of lessons (or key lessons) • Date of next review: • Lessons Learned Syntax • Name, Date • Contributing Factors, Recommended Approach • Topic • Note that both positive and negative lessons are captured – project related success or failure is not discernable