Lesson learnt - project closure

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...

If I am not mistaken, PMBOK clearly mentions that documenting lessons learned is part of the project closure.

My name is Rami Kaibni, thanks !

My apologies, corrected your name.

Thanks Rami. As I indicated in my first response - I could not think of scenario, but still left it as a possibility if Karthik was in such a scenario. Hope that makes sense. I think we are on the same page.

First of all you need to do the contract closure on time. Contract closure needs to be done as per the schedule. Now whether you want to wait for the Lessons Learnt and keep the project open for that depends on your Project Sponsor. Remember, so long as the project is kept open there are budgetary implications of the same. So whether or not a project can be close without waiting for the Lessons Learnt will be the decision of the Project Sponsor in collaboration with the Project Manager

Lots of good thoughts!

Ideally, we would have Lessons Learned before we close a project. If lessons are documented along the way, that makes it less of a burden at the end. If time is scheduled for a review session -- well in advance -- then it should fit nicely. Reality often doesn't work that way. It's not unusual for us to have Lessons learned as a Post-Project activity. Sometimes, sponsors want to see how things play out for a while, before they provide their feedback. The project team may be able to wrap up its own Lessons Learned before the project closes, but the project itself may need to wrap before all stakeholders have provided feedback. The Project Sponsor has the biggest role in determining whether to go that route.