Learned lesson report 1.0.0

Scope

The projects are set up for undertaking unique missions. Often, beside the target there are other elements working together for just one time. These singularities make extremely difficult to rationalize the actual scenario in order to distillate any useful concept that can be reused with proficiency in another project.

The processes are the only elements that maintain a reasonable resemblance with the standards. This reduces the need of specific registers, leaving the task of collecting information about the quality of processes (rules and templates) to the Risk and Issues registers.

When the risks and issues are focused on process, a specific report is necessary for communicating the results from the PMO (Project Assurance) to Sr Management.

Quality

Being the reality made by perceptions, it is essential to understand if the failure (or the potential improvement) can be abstracted (i.e. de-personalized from the person accountable for the process).

During the examination (e.g. Issue Management meeting) all the factors should be weighted in view of the project’s statistics to be analyzed on the basis set (at least) both in Project Mandate and Business Case.

Recommendations shall be approved by the company’s Sr Management.

RACI (who does what)

Operation desc./Roles Owner Spr PM SME BA Stkhd
Assessment of the situation during the meetings C A C C R C
Verifying that all necessary information is:

  1. consisted with the company’s current standards.
  2. estimations are delivered together with the adopted methods.
 I A C I R I
Assessing the feasibility of the preferred option C A C C C C
Compiling the Learned Lessons report I C A C R C
Approving A R C C
Updating whenever the board authorizes it C A R I I I

Distribution list

This report contains highly sensitive information, both for the persons involved and the company assets. The access to the document shall be profiled either in consideration of company needs or stakeholders’ viewpoint.

Recommendations

Registrar section

These are the key fields

Item Notes
Issue / Risk

ID

The “registrar” reference to the source. This includes the following elements:

  1. Event
  2. Effect
  3. Causes/Trigger
  4. Early Warnings?
  5. Priority
Process scrutinized Name of the process as known.
Templates used Full reference to the used document (as stated in the Configuration Management)
Other sources As indicated during the analysis.
Major Risks As resulted from the analysis
Recommendations
Approved by The responsible authority (e.g. PMO supported by Sr Management)

Technical domains

1)      Lessons Reports from other projects

2)      Project mandate or Project Brief

3)      Daily Log, Issue Register, Quality Register and Risk Register

4)      Highlight Reports

5)      Stage Plans with actuals values to be confronted with estimations and their methods

6)      Observation and experience of the project’s processes.

Financial / Commercial domains

1)      Project Brief

Notes