Project Management Lessons Learned: A Guide to Continuous Improvement
Project management is a field ripe with opportunities for learning and growth. Every project, regardless of its outcome, offers valuable insights that can be leveraged to improve future endeavors. This article delves into the importance of capturing and applying lessons learned in project management, drawing from the expertise of industry professionals and highlighting key concepts from Mel Bost's book, "Project Management Lessons Learned: A Continuous Process Improvement Framework."
The Value of Lessons Learned
Lessons Learned is an important phase in project management. At its core, the lessons learned process is about continuous improvement. It's a structured approach to documenting both successes and failures, ensuring that mistakes are not repeated and best practices are replicated. These documented insights reflect an organization's commitment to project management excellence, offering project managers a chance to learn from the experiences of others.
The Role of the Project Management Office (PMO)
The Project Management Office (PMO) plays a crucial role in promoting and facilitating the lessons learned process. A well-functioning PMO provides the framework, tools, and support necessary to effectively capture, analyze, and disseminate lessons learned across the organization.
Empowering the PMO
Mel Bost emphasizes the importance of empowering the PMO to drive process improvement through lessons learned. This empowerment includes providing the PMO with the necessary resources, authority, and support from senior management.
Addressing PMO Challenges
Bost also addresses the challenges that can hinder a PMO's ability to execute its responsibilities effectively. He offers practical advice on how to overcome these obstacles and ensure that the PMO can fulfill its role in promoting lessons learned.
Read also: Lessons in Auto Financing
Actionability: The Key to Effective Lessons Learned
The book emphasizes "actionability," or producing a process improvement that can be acted upon by anyone in the PMO or project team. The focus should be on producing process improvements that can be readily implemented by anyone in the PMO or project team.
The Lessons Learned Process: A Step-by-Step Approach
A Guide to the Project Management Body of Knowledge (PMBOK® Guide) defines a process as a set of interrelated actions and activities performed to achieve a specified set of products results or services (2004, p. 367). The purpose of a lessons learned process is to define the activities required to successfully capture and use lessons learned. The lessons learned process includes five steps: identify, document, analyze, store and retrieve.
Identification
The initial step involves identifying comments and recommendations that hold value for future projects. This requires a proactive approach, encouraging team members to share their observations and insights throughout the project lifecycle. The person who will be facilitating the lessons learned session should prepare in advance. In preparation for the lessons learned session the facilitator should have the participants complete a project survey. The project survey should be organized by category. The use of categories will ensure key information is not missed and will later help to focus the discussion. Standard categories for each project should be defined and additional categories specific to a project can be added. Suggested categories include project management, resources, technical, communication, business processes, requirements, design and build, testing, implementation and external areas. These categories can be subdivided into more detailed categories. For example, project management can be divided into the process groups: initiating, planning, executing, monitoring and controlling and closing. Planning can then be further divided into project schedule, risk analysis, etc. The project survey should also include specific questions for each category. These responses will be used by the lessons learned facilitator to guide the discussion during the lessons learned session.
Documentation
Once identified, lessons learned must be thoroughly documented. This includes capturing the context, the specific issue or opportunity, the actions taken, and the resulting outcomes.
Analysis
After lessons learned are captured, they should be reported to project stakeholders. Different types of reports can be produced based on the audience. The detailed lessons learned report consists of the data captured during the lessons learned session and any additional input from participants who were not able to attend. The facilitator should distribute the detailed lessons learned report to all participants and participants should be given time to respond to the accuracy of the report. After the report is finalized, the entire project team should receive a copy even if they did not participate in the lessons learned session. The facilitator should prepare a summary for leadership. This report should present an overview of the lessons learned process and a summary of project strengths - what went well, project weaknesses - what went wrong and recommendations - what we need to improve. Step three of the lessons learned process is to analyze and organize the lessons learned for application of results. At level 1 analysis is more informal as the team decides what can be done with the lessons learned. Information is shared with other teams during organizational meetings.
Read also: Unveiling Truths in SVU
Storage
To ensure that lessons learned are readily accessible, they must be stored in a central repository. This repository should be easily searchable and well-organized, allowing project teams to quickly retrieve relevant information. Step four of the lessons learned process is to store in a repository. At level 1, organizations do not have a dedicated lessons learned repository in place. Lessons learned documents are stored along with other project documents, normally on a shared drive or in some form of project library. There is no easy means of retrieving the lessons.
Retrieval
The final step involves retrieving and applying lessons learned to current projects. This requires a proactive effort to search the repository for relevant insights and incorporate them into project planning and execution. Step five of the lessons learned process is to retrieve for use on current projects. This is step is rarely used at level 1.
Levels of Lessons Learned Utilization
Organizations vary in their maturity when it comes to lessons learned utilization. Understanding these levels can help organizations identify areas for improvement.
Level 1: Ad Hoc
At level 1 organizations are not routinely capturing lessons learned partly because there is no defined process in place. Lessons learned are handled on a project by project basis with no standardized tools or consistency among projects. At a minimum level 1 organizations may have a meeting where lessons learned are discussed and produce a report summarizing the findings.
Level 2: Defined Process
At level 2 organizations have a defined process and basic tools for identifying and documenting lessons learned. The process has become part of the organization’s culture and is consistently applied to projects and process documents have been revised to allow for more efficiency. What organizations need at level 2 are effective tools and the beginning of analysis of stored lessons learned.
Read also: Recovering from Wildfires
Tools and Techniques for Effective Lessons Learned
Several tools and techniques can enhance the effectiveness of the lessons learned process.
Project Surveys
In preparation for the lessons learned session the facilitator should have the participants complete a project survey. The project survey should be organized by category. The use of categories will ensure key information is not missed and will later help to focus the discussion. Standard categories for each project should be defined and additional categories specific to a project can be added. Suggested categories include project management, resources, technical, communication, business processes, requirements, design and build, testing, implementation and external areas. These categories can be subdivided into more detailed categories. For example, project management can be divided into the process groups: initiating, planning, executing, monitoring and controlling and closing. Planning can then be further divided into project schedule, risk analysis, etc. The project survey should also include specific questions for each category. These responses will be used by the lessons learned facilitator to guide the discussion during the lessons learned session.
Lessons Learned Input Form
As mentioned earlier, the identification of lessons learned from each project is the primary responsibility of each project manager. During this level, organizations need to dedicate a resource or resource(s) to begin the analysis of documented lessons learned. The purpose of the analysis is to identify actions that can be taken within the organization to strengthen weak areas of knowledge and implementation during each project. This can be done through enhanced training of project managers and/or team members; this includes project sponsors and champions. It is also important that gathering the original lessons learned data should be collected utilizing consistent processes and forms. Consistency of input information allows for speedier identification of reoccurring issues and proactive resolutions. The lessons learned input form is a key tool. This document allows for more consistent data collection as well as provides a means for easier retrieval. The lessons learned template should include previously agreed to fields such as: category, lesson learned, action taken, how did you arrive at the action taken, root cause and key words. Key words should always be identified. Key words are ultimately one of the determinants of success in utilizing lessons learned (Prichard, 1997, p. 94), and are essential for easy retrieval. The data on the lessons learned input form is transferred to the organization’s lessons learned repository. The lessons learned input form can also be shared with the project team during the lessons learned session.
Reporting
At level 1, organizations should be able to produce lessons learned detailed and summary reports from information gathered during the team sessions and share these reports with immediate project stakeholders. Recommendations - recommended actions to be taken to correct findings. The approved actions should be documented and tracked to completion. During Level 2 we noted that organizations should have identified process and templates in place to address lessons learned. Analysis of lesson learned data was discussed. So the executive-level lessons learned report should be no more than 3 pages to ensure that the data is read and decisions should be easy to determine. The 3 page report should consist of: Page 1 - text overview of analyzed data including recommended next steps…improvement or recognitions. The most successful graphical presentations display either pie charts or bar charts with easily understood x-axis and y-axis titles.
The Importance of Reflection and Changing Attitudes
Bost emphasizes the importance of reflection and changing attitudes in lessons learned. This involves encouraging project teams to critically examine their experiences, identify areas for improvement, and be open to new ways of doing things.
Integrating Lessons Learned with Risk Management and Knowledge Management
Bost highlights the interconnectedness of lessons learned, risk management, and knowledge management. He argues that these three disciplines should be integrated to create a holistic approach to project improvement.
The Sustainability Imperative
Bost also addresses the sustainability imperative in project management. He emphasizes the importance of considering the long-term environmental, social, and economic impacts of projects.
The Human Element: Overcoming Challenges and Fostering Collaboration
Communication and Transparency
Communication and transparency are two of the most crucial aspects in a project. In matrix organisation environment these days, it has been even more challenge for PMs to keep your resources motivated even though it is available with in your company as they may be more loyal to other project or PM them your project and you. This issue has been even greater when the resources has been from vendor as the resources may not have commitment for our project as we expect. Though all these problems are part of our PM life, we can overcome by applying right approach for different problems.
Negotiation Skills
While working with resource managers and external sources, I found the need to acquire and master communication and negotiation skills. That helped me to get the best resources, while also sometimes allowing other projects to have the resource I was pursuing.
Motivating Resources
Chinese Army Approach, what a good way of thinking resources are unlimited and are in the demand of PM. In the real world, every single hour spent by each resource is chargeable and PM is responsible for it. Communication is the key element in resolving the resource demanding and planning activities, PM can only take charge if the resources are on board with full commitment and no other interruptions from other projects.
Real-World Examples and Case Studies
The Panama Canal Expansion Project
Mel Bost has conducted lessons learned training in Dubai and in Panama for the Canal Expansion Project.
tags: #lessons #learned #book #project #management
