Which strategies are the most recommended to make efficient use of lessons learned?
There are companies that have similar projects and make the same mistakes even though they have records of lessons learned. How can this situation be improved? Saving Changes...
I always advise that every project --- at every stage --- and by every discipline --- and for every process (process group), the PMT (Project Management Team) must review all of the relevant lessons learned during planning the stage work.
...
1 reply by Carlos Eduardo Escobar Muentes
Oct 20, 2017 3:36 PM
Carlos Eduardo Escobar Muentes
...
I agree, the point maybe to consider is that sometimes the project team is not the same. I think that is where the PMO must act because many times the team of a current project does not know of the existence of similar projects that were done previously by other people.
regards
Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
The question is what is done with them once collected? Where do they go? Is there a standardized format? Are they accessible; searchable? Or do they sit in a lost directory or dusty file cabinet.
...
1 reply by Carlos Eduardo Escobar Muentes
Oct 20, 2017 3:42 PM
Carlos Eduardo Escobar Muentes
...
I think that's the problem. What can be done to improve that ?. On the one hand it may be accessible and there is ignorance. There may be knowledge about the existence of previous projects but there is no adequate guide to reach the lessons learned. I think it is something that can be improved even with simple actions but requires the commitment of the organization.
Saving Changes...
David KachouiDirector of Business Development| Natech PlasticsNew York, Ny, United States
I didn't found that a separate lessons learned document worked. I moved to incorporate the lessons learned into the process in some way. This could be an update to an instruction on a form, update to a Work Instruction, etc.
1. Collect them over the life of a project
2. Categorize and respond to them appropriately - reminders need to be handled different from organizational blockers and those are handled different from true knowledge
3. Ideally, bake them into your standards & SOPs
Kiron
...
1 reply by Carlos Eduardo Escobar Muentes
Oct 20, 2017 3:45 PM
Carlos Eduardo Escobar Muentes
...
Thank you very much Kiron for your contribution.
I will review the post in the links
regards
Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
Following Andrew, lessons learned need to be easily searchable and accessible. In an environment with many projects you might need a person dedicated to organizing the lessons learned, who keeps aware of all the projects and their business goals, and shares applicable lessons with PMs as required. I believe a Business Analyst would be a good candidate for this position.
...
2 replies by Carlos Eduardo Escobar Muentes and Jess De Ocampo
Oct 20, 2017 3:48 PM
Carlos Eduardo Escobar Muentes
...
Depending on the environment I find it interesting to have someone focused on the efficient distribution of lessons learned. Obviously if there are many projects it will not be an easy task to relate them, however it can be scalable.
Thank you
Oct 23, 2017 4:04 PM
Jess De Ocampo
...
I agree. There should also be a repository for these lessons learned. How about discussing one topic about lessons learned during coffee breaks and initiate an interactive discussion and inputs from the team as a refresher?
I agree, the point maybe to consider is that sometimes the project team is not the same. I think that is where the PMO must act because many times the team of a current project does not know of the existence of similar projects that were done previously by other people.
The question is what is done with them once collected? Where do they go? Is there a standardized format? Are they accessible; searchable? Or do they sit in a lost directory or dusty file cabinet.
I think that's the problem. What can be done to improve that ?. On the one hand it may be accessible and there is ignorance. There may be knowledge about the existence of previous projects but there is no adequate guide to reach the lessons learned. I think it is something that can be improved even with simple actions but requires the commitment of the organization. Saving Changes...
I didn't found that a separate lessons learned document worked. I moved to incorporate the lessons learned into the process in some way. This could be an update to an instruction on a form, update to a Work Instruction, etc.
1. Collect them over the life of a project
2. Categorize and respond to them appropriately - reminders need to be handled different from organizational blockers and those are handled different from true knowledge
3. Ideally, bake them into your standards & SOPs
Kiron
Thank you very much Kiron for your contribution.
I will review the post in the links
Following Andrew, lessons learned need to be easily searchable and accessible. In an environment with many projects you might need a person dedicated to organizing the lessons learned, who keeps aware of all the projects and their business goals, and shares applicable lessons with PMs as required. I believe a Business Analyst would be a good candidate for this position.
Depending on the environment I find it interesting to have someone focused on the efficient distribution of lessons learned. Obviously if there are many projects it will not be an easy task to relate them, however it can be scalable.
