|
Definition: Editors' Note: The term “Lessons Learned” is identified in the PMBOK® Guide—2000 Edition as an output falling under several areas within the Controlling Processes. “The causes of variance, the reasoning behind the corrective action chosen, and the other types of lessons learned should be documented so that they become part of the historical database for both this project and other projects of the performing organization.” (p. 49)
Acceptance Level: Generally accepted
Alternative or Related Terms: Lessons Learned Capture; Best Practices, Project Record
Application Areas/Intended Uses: Lessons Learned is listed as an output under Project Integration Management, Project Time Management, and Project Cost Control. Considered very valuable as a source of information used in mid-project or next-project changes and corrections.
Chief Advantages: Provides assessment, from multiple viewpoints, of aspects of a project that could have been done better, or that were particularly successful, so further mistakes can be avoided and successful practices can be further developed and applied.
Additional Reading:
Best Practices Lessons Learned (BPLL): A View from the Trenches. Marsha Frank Berke.
PMI 2001 Seminars & Symposium Proceedings, Nashville, Tennessee USA.
Best Practices—The Nine Elements to Success. James N. Salapatas. PMI 2000 Seminars & Symposium Proceedings, Houston, Texas USA.
Gathering and Using Lessons Learned. Adrian Abramovici. PM Network, October 1999, 61- 63.
How to Capture Innovations, Solutions, and Lessons Learned Across Product Teams:
Implementation of a Knowledge Management System. Carol Stephens, PMI 1999
Seminars & Symposium Proceedings, Philadelphia, Pennsylvania USA.
Implementing a Lessons Learned Process That Works. Michael S. Terrell. PMI 1999
Seminars & Symposium Proceedings, Philadelphia, Pennsylvania USA.
Lessons Learned Through Process Thinking and Review. George Pitagorsky. PM Network, March 2000, 35-38.
Vanquishing PM Nightmares. Peter Weaver. PM Network, January 2002, 40-43. |
