Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
No you can't - It is an essential part of project closure to make sure lessons learned are recorded by Everybody (All Stakeholders). Saving Changes...
Karthik TSenior Engineering Manager| NikeBangalore, Karnataka, India
Thanks Rami Kaibni,
What if relavent stakeholders left the company or don't respond it on time. How long project manager can wait on this? What could be an alternative approach? Saving Changes...
Conrad KolisSenior Manager Project Management| ConvergysCincinnati, Oh, United States
One approach is for the project team to document whatever they can, then forward to stakeholders for validation and amendment. Some stakeholders may feel that they have even less time now that they are in operational mode, so it helps to give them something to start with. If you provide them a "starter" list, they may take at least some brief time to comment, and, if you're lucky, they may provide a few additional lessons.
It may not be the best way, but if you can't get a response, then it might help. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
It will depends on your governance process. In my case, to complete lessons learnt is needed to get the go to project closure stage gate. Saving Changes...
Karthik TSenior Engineering Manager| NikeBangalore, Karnataka, India
Thanks everyone for your inputs.
If lesson learnt updation is such a mandatory task for closing the project, then in the above scenario we can't close the project. So, how long a project can be in this state? What will happen to the resources allocated for the project? When can we release them?
In worst case, if we don't get any response from stakeholders on lesson learnt, can we get approval from project sponsor to close the project?
Hope I'm not thinking something irrelevant :)
--
Regards,
Karthik
...
2 replies by Prashant Sonwane and Rami Kaibni
May 26, 2016 11:20 AM
Rami Kaibni
...
You are probably over thinking the matter - Lessons learned are gathered and documented throughout the project, not in the last moment so making sure all lessons learned are documented properly should not be a big deal for closing the project.
We've done this for a $10 Mil and for a $500 Mil jobs and if tackled from the beginning, it will go smooth !
Apr 20, 2017 6:54 AM
Prashant Sonwane
...
I think "Lessons Learnt" activity needs to be followed internally in the organization so that in future projects we should not repeat any similar mistakes. I guess Lessons Learnt doesn't directly relate with Project deliver or release. Hope this make sense.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
May 26, 2016 11:14 AM
Replying to Karthik T
...
Thanks everyone for your inputs.
If lesson learnt updation is such a mandatory task for closing the project, then in the above scenario we can't close the project. So, how long a project can be in this state? What will happen to the resources allocated for the project? When can we release them?
In worst case, if we don't get any response from stakeholders on lesson learnt, can we get approval from project sponsor to close the project?
Hope I'm not thinking something irrelevant :)
--
Regards,
Karthik
You are probably over thinking the matter - Lessons learned are gathered and documented throughout the project, not in the last moment so making sure all lessons learned are documented properly should not be a big deal for closing the project.
We've done this for a $10 Mil and for a $500 Mil jobs and if tackled from the beginning, it will go smooth ! Saving Changes...
Karthik TSenior Engineering Manager| NikeBangalore, Karnataka, India
That's great Rami Kaibni. Completely agree with you. I know its ongoing task throughout the project. Not a complex thing. Agreed.
I raised this topic wrt to PMP exam question which was like this. Just collecting various thoughts / experiences around this.
Thank you all.
-- Regards, Karthik
...
1 reply by Rami Kaibni
May 26, 2016 11:39 AM
Rami Kaibni
...
If I am not mistaken, PMBOK clearly mentions that documenting lessons learned is part of the project closure.
As Sergio mentioned, I also relate it to the Governance process. If documenting Lessons Learned is not important to your organization (I don't know of any scenario where at least something cannot be gleaned), then you skip it and move on... I would be very concerned if you are holding off from releasing resources from the project just because the Lessons Learned process is not completed. I frequently follow the process that Conrad indicated.
If sticking to the letter of the process is important, then there better be enforcement of each step... i.e. enforce the participation in Lessons Learned so you can release the resources and move on to the next thing Saving Changes...
Yes, agreed Rami... LL is part of project closure. However, I usually go to 1.1 Purpose of the PMBOK Guide, the definition of 'good practice' etc., and interpret it as 'everything is negotiable'... If it doesn't fit your organization / your situation, then you can omit it.
Open to your feedback...
...
1 reply by Rami Kaibni
May 26, 2016 11:56 AM
Rami Kaibni
...
I do not disagree with you at all Samuel - This applies to all aspects of project management.
However, Lessons Learned specifically are very important for future projects success and improvement of the organization. Can you give me on example where you've heard that Lessons Learned did not fit any organization ?
Community Champion
