The Slides briefly show what are the main characteristics of performing a lessons learned. In this case - it was in relation to an SAP S/4 Hana Implementation The knowledge gained during a project which shows how project events were addressed or should be addressed in the future for the purpose of improving future performance.

1. © - Konnect Prime 2008 - 2017
Lessons Learned:
The knowledge gained during a project which shows how project events were
addressed or should be addressed in the future for the purpose of improving future
performance.
Konnect Primes
Lessons Learned
A Typical Approach

2. © - Konnect Prime 2008 - 2017
Project Lessons Learned: Normal characteristics of a lessons learned
Typical Lessons learned have detailed analysis on the following project performance indicators
• Time
• Did the training team meet their agreed deadline and was the output of the team in line with the deadlines
communicated to them?
• Resources
• Did the team capabilities match the needs of the project and was the RACI adhered to or were the resources
spread too thin and over allocated constantly?
• Quality/Scope
• Were the objectives and outcomes outlined in the Project Charter adhered to and reviewed on a regular
basis? If not, why not?
• Cost
• Were budgetary targets met, and if not what was the percentage of deviation and why? Did we meet our
budget of $1.9 Million or did we go over it by 1% acceptable or 50% unacceptable?
• Risk
• Where the risks identified early and managed successfully or mitigated? Did the project team collectively
review the Risk Register and understand its impact on the organization or leverage change orders to address
scope creep?
Examples in italics from previous projects

3. © - Konnect Prime 2008 - 2017
Project Lessons Learned: Normal characteristics of a lessons learned
Typical Lessons learned have detailed analysis on the following project performance indicators
• KPI Analysis
• Did the Project meet/exceed the goals of the KPIs outlined at the beginning of the project? If not, why?
Note: KPIs must be objectively measurable.
• Review of Pivotal Points/Dates in the project and how they impacted the overall outcome of the project
• Did the various stakeholders agree that deadlines were attainable with the team in hand such as the date
for signing off test scripts?
• Review of any feedback provided by External Auditors or Advisors and if it was incorporated into the lesson
learned
• Did we listen to all points of view and provide feedback to them why it was not adopted ?
• Review of Pivotal Points in the project and how they impacted the overall outcome of the project
• Was a decision made by an individual to release code to production that was not properly tested?
• Review of Statements of Work
• Did the Vendors meet their agreed Statements of Work and if not – were the deviations from the SoW
within acceptable tolerances and were they mutually agreed before the deviation?
Examples in italics from previous projects

4. © - Konnect Prime 2008 - 2017
• Review of the organizational structure
• How effective were key players at each phase of the project and what remediation was needed
before the next projects – e.g. training or change the line of communication for the next project
• Review of Required Documentation
• What document objects were successful in terms of (BPML , BPDS etc ) and which ones were not
and why – too confusing, author did not convey the importance of the document? Was there
documentation that was needed/missing?
• Review of Project Processes and Governance
• Which Project Processes were effective in terms of “driving the project home” and which ones
were had no tangible benefit?
• What Project Meetings and their attributes such as attendees, documentation and duration –
were useful? Which ones could be eliminated?
• Review of Stakeholder management
• Were the Stakeholders expectations managed in terms of Project Delivery etc.
Examples in italics from previous projects
Project Lessons Learned: Normal characteristics of a lessons learned
Typical Lessons learned have detailed analysis on the following project performance indicators

5. © - Konnect Prime 2008 - 2017
Konnect Prime Approach to Lessons Learned: In Conclusion
At lot of analysis is usually spent on perception of a project which is beneficial but this needs to converted
into actionable tasks and definitive metrics so that it becomes a Long Term Organizational Process Asset for
the PMO team – e.g. 89% of PMs think that a formal constructive Lessons learned database is important
but only 12% actually do it. ( sourced from www.pmi.org)
An approach KP has found to work in the past in relation to lessons learned is as follows. This approach
avoids the risk of merely lesson logging or perception noise.
Change or
Performance
impact
Cause Lesson Learned Action Process Change
Product is not
what customer
expected
No prototype was given to
customer for approval
Product Builder must
provide prototype that
meets nn% of
requirements
Request a change to the
SoW to ensure that
prototyping is included
Map requirements to
User Cases/Prototypes
and ensure that sign off
include this step