Published
This document together with attachments presents guidance to capture “Lessons Learned” for Pilot projects.
This CWA can be used as the boilerplate for “Lessons Learned”, that is information pertinent to experiences and insights captured before, during and immediately after conducting a Pilot.
Lessons Learned is a loosely and open ended term, but is typically used as the collective moniker for a document that compiles information about an event (project, pilot, task etc.) with the purpose to obtain knowledge about one or more areas. The end goal of the Lessons Learned effort is put in other words to improve something, something being a process, the way an individual task is executed, user support, information access, quality of services and more.
The target group for the Lessons Learned report might vary depending on the subject for the Lessons Learned. In this case, the Lessons Learned report will most likely be of greatest value to the management and the stakeholders of the PEPPOL project.
The method used to capture the information necessary to create a Lessons Learned is in essence based on the notion that several elements of the Pilot Support Guidelines Framework will be used to collect the information that constitute the Lessons Learned. The Guidelines referred to in the previous sentence are the Evaluation, Test and Pilot Execution Guidelines.
Given the “distributed collection” model, it is important to understand how the different Guidelines entities are related:
PUBLISHED
DS CWA 16073-4:2010
60.60
Standard published
Dec 9, 2011