George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
Do you believe that technology companies SHOULD have a specific lessons learned methodology in place?
Yes, it is a must. If a company does not have one, they are NOT in the correct path.
Maybe, it is entirely optional. If a company does not have one, they could use alternative methods.
No, it is NOT a must. It is not a critical factor for current organizations; there are other priorities and lessons learned process could be very expensive. Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
PMI PMBOK defines lessons learned as the learning gained from the process of performing the project. Formally conducted lessons learned sessions are traditionally held during project close-out, near the completion of the project. However, lessons learned may be identified and documented at any point during the project's lifecycle.
The purpose of documenting lessons learned is to share and use knowledge derived from experience to (a) Promote the recurrence of desirable outcomes (b) Preclude the recurrence of undesirable outcomes. Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
As a practice, lessons learned includes the processes necessary for identification, documentation, validation, and dissemination of lessons learned. Utilization and incorporation of those processes includes identification of applicable lessons learned, documentation of lessons learned, archiving lessons learned, distribution to appropriate personnel, identification of actions that will be taken as a result of the lesson learned, and follow-up to ensure that appropriate actions were taken. Saving Changes...
Should a company have a specific technology in place?
A company should have a specific procedure, Yes. Is ONE methodology fit for all project? not sure Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
As a program manager, I truly believe that applying lessons learned within technology companies produce short-term costs benefits.
Just as indicated by Rhodes and Dawson (2013, p.1) there are lessons learned from using experiences learned, which describes problems and benefits in applying lessons learned from projects within the project management department of a large, information-intensive organization.
So, in summary, the secret lies in the how, when and why you are applying a lessons learned methodology, and most importantly, how your knowledge management is updated, shared and published so that the results are accessible and easily grouped. Saving Changes...
Yes, It was my biggest weakness point and hard lessons was learned and now I advocate and practice it on personal and professional level. Yes I document everything Saving Changes...
Paul HollingsIT Project Manager| Self EmployedHerne Bay, Kent, United Kingdom
It's a "YES" from me. Lessons learned is a vital element of project management. How often do we hear of costly mistakes being repeated over and over...? Lessons learned benefit every aspect of the iron triangle!!
Unfortunately, it is difficult to implement. Too often it is not seen as achieving anything directly related to the project and therefore falls down the priority list, especially in busy environments. I have historically experienced low participation where feedback and sessions are concerned.
Lessons learned need to be included in the project deliverables, you then have a means of escalating a lack of interest as an issue. Of course, this requires upper management to buy in to the need for the activity to take place and follow through if it doesn't. Saving Changes...
For me it is a partial "yes". There is tremendous value in an effective lessons learned process but like all other practices, it needs to be tailored to fit the context of a given project. So from an outcome perspective, lessons should be captured, curated, massaged and reviewed, but how that gets done should allow flexibility on the part of project teams otherwise we are back to "checklist project management".
Kiron Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
EL PMI-PMBOK define las lecciones aprendidas como el aprendizaje obtenido del proceso de ejecución del proyecto. Las sesiones de lecciones aprendidas llevadas a cabo formalmente se llevan a cabo tradicionalmente durante el cierre del proyecto, cerca de la finalización del proyecto. Sin embargo, las lecciones aprendidas pueden identificarse y documentarse en cualquier momento durante el ciclo de vida del proyecto. El objetivo de documentar las lecciones aprendidas es compartir y utilizar el conocimiento derivado de la experiencia para (a) Promover la recurrencia de los resultados deseables (b) Evitarla recurrencia de resultados indeseables.
Como práctica, las lecciones aprendidas incluyen los procesos necesarios para la identificación, documentación, validación y difusión de las situaciones del proyecto. La utilización e incorporación de esos procesos incluye la identificación de las lecciones aprendidas aplicables, la documentación de las lecciones aprendidas, el archivo de las lecciones aprendidas, la distribución al personal apropiado, la identificación de las acciones que se tomarán como resultado de la lección aprendida y el seguimiento para asegurar que se tomen las acciones correctivas apropiadas.
Como gerente de proyectos y programas, realmente creo que aplicar las lecciones aprendidas dentro de las compañías de alta tecnología, produce beneficios en costos del proyecto y esto a corto/mediano plazo.
Tal como lo indican Rhodes y Dawson (2013, p.1), hay lecciones aprendidas del uso de las experiencias aprendidas, que describen los problemas y los beneficios al aplicar las lecciones aprendidas de los proyectos dentro del departamento de gestión de proyectos de una gran organización con gran cantidad de información.
Entonces, en resumen, el secreto reside en cómo, cuándo y por qué está aplicando una metodología de lecciones aprendidas, y lo más importante, cómo se actualiza, comparte y como publica la gestión de ese conocimiento para que los resultados sean accesibles para todos. Saving Changes...
George FreemanThought Leader | Author | Architect| Florida, United States
George, I believe organizations should have a “lessons learned” device in place, but I find the written-word to often is the lost-word, meaning that once the lessons learned are documented they go into a black hole even when you have a process in place that demands its review.
In my opinion the PM must model the lessons and be an advocate for communicating it as required to the team as a whole. I recently published an article on strategic lessons learned giving the lessons a bit of a spin to make them more interesting as I find that most individuals find LL boring and not worth the effort to proactively review.
...
1 reply by smith santamaria
Nov 26, 2019 11:46 AM
smith santamaria
...
George, great argument! Indeed most of company that use this technical, at the end put together all that valuable information and throw it in a waste basket.
It's really important share this kind of info to everyone.
George, I believe organizations should have a “lessons learned” device in place, but I find the written-word to often is the lost-word, meaning that once the lessons learned are documented they go into a black hole even when you have a process in place that demands its review.
In my opinion the PM must model the lessons and be an advocate for communicating it as required to the team as a whole. I recently published an article on strategic lessons learned giving the lessons a bit of a spin to make them more interesting as I find that most individuals find LL boring and not worth the effort to proactively review.
George, great argument! Indeed most of company that use this technical, at the end put together all that valuable information and throw it in a waste basket.
It's really important share this kind of info to everyone. Saving Changes...
