When I worked with the Air Force years ago, they had a requirement for every program to capture lessons learned when the product was delivered. The programs that I worked with faithfully carried out this mandate and developed reams of reports that were compiled as lessons learned databases. Unfortunately, there was no requirement to review these databases in anticipation of new starts or to make policy/procedure corrections. As a result, the suggestions and experience that they contained was often lost. Let’s see what we can do to fix this at each of the levels of retrospective.
Advisor
Making Retrospectives Useful, Part II: Doing Something with Lessons Learned
Posted March 7, 2019 | Leadership | Technology |
About The Author
Donald J. Reifer is recognized as one of the leading figures in the fields of software engineering and management, with more than 40 years of progressive management experience in both industry and government. He has built businesses, managed key programs, and led major R&D initiatives. Mr. Reifer is often called upon by clients to review troubled programs, examine red team proposals, and perform competitive assessments with an emphasis on… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.