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...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
The lessons learned must translate into new/improved organizational process assets. Given that OPAs are input to a new project, that project will automatically incorporate the organization's lessons learned repository.
...
1 reply by Carlos Eduardo Escobar Muentes
Oct 23, 2017 11:00 AM
Carlos Eduardo Escobar Muentes
...
totally agree. The important thing is that the organization really handles these procedures with due importance
The lessons learned must translate into new/improved organizational process assets. Given that OPAs are input to a new project, that project will automatically incorporate the organization's lessons learned repository.
totally agree. The important thing is that the organization really handles these procedures with due importance
Thank you Saving Changes...
Jess De OcampoLean Six Sigma Professional/Project Manager/Consultant/| .Manila, Ncr, Philippines
Oct 20, 2017 11:06 AM
Replying to Eric Simms
...
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.
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?
...
1 reply by Carlos Eduardo Escobar Muentes
Oct 23, 2017 4:49 PM
Carlos Eduardo Escobar Muentes
...
In Agile there is something similar to what you mention. In the retrospectives of Scrum for example it is analyzed among the members of the team that things can be improved, which went wrong. Usually it is in a friendly environment some make "lean cofffe" and it is quite productive.
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?
In Agile there is something similar to what you mention. In the retrospectives of Scrum for example it is analyzed among the members of the team that things can be improved, which went wrong. Usually it is in a friendly environment some make "lean cofffe" and it is quite productive.