Lessons learned to be accessible need to be well structure. Do you have define way to do it (template) or should it be just plain text. Saving Changes...
Lisa FunderburgSenior Program/Project Manager| GovernmentBroomfield, Co, United States
Apr 19, 2017 6:54 PM
Replying to Vincent Guerard
...
Thanks,
So your project just get one LL at the closure.
Do I understand that your LL meeting you identify things that need to be improve, and request solutions from participant?
Not necessarily one LL meeting, that's just one where it lives. For longer projects, we will do them throughout and then collect them into that production turnover document.
It depends on the team and my relationship, most times I give them a prompt and then sit quiet and record. This is their time to really reflect and review- things that need to improve, things that went right, processes to update, things we have control over, things we have no control over, vendor issues, internal/PMO issues, etc. I contribute to keep the conversation rolling. If I need, I can structure it more but I typically don't say "okay, now we're going to review the planning phase. What can you tell me about it", unless the team/conversation is stifled and need more direction. Saving Changes...
In my project work I have used a variety document types to develop a Lessons Learned. One of the ways I structure it is with the audience in mind. I may have a different report that is part of the project documentation and one that is part of the project closeout report.
The Close-out report may be structured for the Stakeholders and their requirements for the project and the priority the project had within their area. Depending on the type of project I try not to make this document too technical and to Nasrullah's point more like a story.
For the project documentation and the for future information this document would contain all of the technical issues that affected the project. I make sure I deconstruct the project so when I have to do a repetitive type of project I can use it for reference.
...
1 reply by Vincent Guerard
Apr 24, 2017 6:01 PM
Vincent Guerard
...
Lessons Learned is a great input for risk on future project, it need to be structure in way way that is usable.
You seem to have a great way to do it.
Thanks for sharing
Saving Changes...
Ananthaiah Ramesh SegavaluSAP Project Manager Program Manager Technical Lead| GlobalPoint IncProsper, Tx, United States
Does any one can share a template in Excel or PPT?
...
1 reply by Vincent Guerard
Apr 24, 2017 6:04 PM
Vincent Guerard
...
Look under template and deliverables in this site you will find a few.
One may be for your need.
I tend to approach my lessons learned as more of a workshop. We'll have post its and group them together at the end. It'll go something like this:
1) intro into what we're doing
2) Each participant writes things that went well, things that could be done better. It's a duration of 5-10 minutes maximum
3) There are two sheets of paper, what went well, what could be improved. Everyone goes up to the sheets and puts their stickers on there. As they put them on there, they organically group them
4) We go through the list together and for the items where they could be improved, we discuss the point, come to an agreement on what we could better, document this.
5) At the end we have a list of: WELL DONE's and a list of: Better next times.
6) We then upload these as part of the closure of the project and then communicate both of them to the PMO to provide a clear list for future projects.
In my previous companies we have gone through the lessons learned of previous projects at the start of a project to try and mitigate these issues happening again. It helps us to see the road a little clearer
...
1 reply by Vincent Guerard
Apr 24, 2017 6:06 PM
Vincent Guerard
...
Look like a very organize way. Yes Lessons Learned can be a great source of information for futur project provide they are well documented.
Thanks for sharing
In my project work I have used a variety document types to develop a Lessons Learned. One of the ways I structure it is with the audience in mind. I may have a different report that is part of the project documentation and one that is part of the project closeout report.
The Close-out report may be structured for the Stakeholders and their requirements for the project and the priority the project had within their area. Depending on the type of project I try not to make this document too technical and to Nasrullah's point more like a story.
For the project documentation and the for future information this document would contain all of the technical issues that affected the project. I make sure I deconstruct the project so when I have to do a repetitive type of project I can use it for reference.
Lessons Learned is a great input for risk on future project, it need to be structure in way way that is usable.
You seem to have a great way to do it.
Thanks for sharing Saving Changes...
I tend to approach my lessons learned as more of a workshop. We'll have post its and group them together at the end. It'll go something like this:
1) intro into what we're doing
2) Each participant writes things that went well, things that could be done better. It's a duration of 5-10 minutes maximum
3) There are two sheets of paper, what went well, what could be improved. Everyone goes up to the sheets and puts their stickers on there. As they put them on there, they organically group them
4) We go through the list together and for the items where they could be improved, we discuss the point, come to an agreement on what we could better, document this.
5) At the end we have a list of: WELL DONE's and a list of: Better next times.
6) We then upload these as part of the closure of the project and then communicate both of them to the PMO to provide a clear list for future projects.
In my previous companies we have gone through the lessons learned of previous projects at the start of a project to try and mitigate these issues happening again. It helps us to see the road a little clearer
Look like a very organize way. Yes Lessons Learned can be a great source of information for futur project provide they are well documented.
Thanks for sharing Saving Changes...
Shivaram Y.SDirector| Vivin SynergySharjah, Sharjah, United Arab Emirates
Lessons Learnt as per me, are to be easily accessible, organization - wide appreciated and used on an ongoing basis, if the company is project based would have necessary filters such as discipline such as engineering, management, quality control, project reference, who initiated, who moderated, who approved and what action is suggested , root cause analysis, procedural requirements, resolved, closed etc. and is used for lessons learned workshops for newly awarded projects. There can be workshops with Client / Contractor wherein all participants contribute in synergy. Same can be used for risk management also.
...
1 reply by Vincent Guerard
Mar 31, 2018 9:40 PM
Vincent Guerard
...
Shivaram,
Very good approach, a lot like Prince2 teach.
Saving Changes...
Tom ConnollyCEO| TCA Coaching and Training LtdCork, County Cork, Ireland
I find that the best way to collect lessons learned is in a final project review meeting with as many of the team as possible. I used to call this the "Post Mortem" in a less politically correct age. My formula for running these meetings is:
- Start with celebrating success. We’re done! It is achieved! The project is finished and we got to the line!
- Brainstorm a list of what went well. Use the proper brainstorming technique to ensure everybody’s input is harnessed.
- Brainstorm a list of what did not go well. Position this as “What could we have done better?” Start off that list yourself with what you personally as project manager could have done better. That makes it safe for people to admit their own mistakes. You will end up with a big list.
- Shorten that list by asking “What SHOULD we have done better”.
- Then shorten that to “What WILL we do better next time?”
- Then commit to including these lessons in the Scope of the next similar project so that they become goals of that project - so they will get done.
I think templates are a great simple way to ensure this happens - enforce the use of templates for Scope and Goal documents by all project managers and make sure the Lessons Learned from previous Projects is a compulsory field.
The easiest way I think to ensure this is to make it easy for the PM so that they can access the historical Lessons Learned in the same place as they download the template.
...
1 reply by Vincent Guerard
Mar 31, 2018 9:42 PM
Vincent Guerard
...
Tom,
Nice structure, should you do it more than just at the end, when more people are available and memory is fresh.
Saving Changes...
Betsy GreenOnboarding Manager| TownNews.comMoline, Il, United States
I'm working on improving Lessons Learned in my company. Here's my current approach, which is a work in progress:
- At the end of each project phase, I send stakeholders a SharePoint survey, in which they evaluate phase-specific accomplishments and give general project feedback. The survey is anonymous.
- I summarize those results and share them at a core team meeting so that we can make any adjustments or improvements as the project progresses.
- At the end of the project, I send another anonymous survey through SharePoint. Participants evaluate the project as a whole and provide feedback.
- Next, I schedule a formal Lessons Learned meeting. I ask all of the participants to come with three successes and three areas of improvement.
- During that meeting, participants share those lessons and brainstorm others. A facilitator writes them on a whiteboard. Right now, the facilitator is the PM, but I'd like to try asking a PM who did not work on the project to lead the discussion.
- After the brainstorming and review are complete, I ask participants to get up and put marks by the three positives and negatives that they think were most important.
- The successes/improvements learned from that meeting are categorized, then summarized several places: a Lessons Learned document specific to the project, in the Project Close Report, and in a spreadsheet that is shared by all PMs.
- Once a month, in our larger team meeting, any PM who has closed a project shares the lessons learned with the rest of the group.
...
1 reply by Vincent Guerard
Mar 31, 2018 9:44 PM
Vincent Guerard
...
Betsy,
Like I ask Tom, should you do those meeting more than just at the end?
Love can sweep you off your feet and carry you along in a way you've never known before. But the ride always ends, and you end up feeling lonely and bitter. Wait. It's not love I'm describing. I'm thinking of a monorail.
