Search:

ProjectConnections Print View


Got a Question?
Drop us an email, or call us toll free:
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.


Learn more about ProjectConnections and who writes our content. Want to learn more? Take a site tour and compare our membership levels.


Get Instant Access to Over 200 Templates and Hundreds of Resources
Become a Member »

Lessons Learned Meeting Agenda


Quick Summary
A sample agenda for a lessons learned meeting, to capture what did or didn't go well on a project, how to replicate success, and what to do differently in the future.


The template requires a free Member account
Please log in to download the file. Don't have a log in? Register now, it's fast and free!
Log in to download this file

Username:  
Password:  

What this is

An example agenda for a half-day lessons learned meeting at the end of a project (sometimes called a Project Closeout Meeting). It includes:


Why it's useful

The only way to avoid problems happening yet again in the future is carefully consider what went wrong and why, and make sure there is a way to transfer related recommendations forward. Likewise teams can help others repeat their successes only if they somehow can express concretely what went well, and why. The specific lessons and recommendations generated in this kind of meeting will yield concrete actions for other teams.

NOTE: This agenda is also useful for interim lessons learned meetings. Some teams have such meetings at the end of each major project phase to capture lessons before the team moves on (and perhaps forgets the fine points of lessons learned so far).


How to use it

  1. Edit the example agenda subjects to reflect any specific areas or descriptions of what your meeting should cover. Adjust the timeslots for a longer or shorter meeting depending on your project and how much discussion you think will be needed.

  2. Adjust the attendee list to include specific names and their departments/functional groups, to help ensure that you're inviting everyone that should be there.

  3. Check this draft invitee list with your core team and solicit ideas for who else should be invited. Often team members will think of key individuals who might have been a heavy participant at some point, with valuable information to relay. For instance, "We should invite Joe, he had to deal with all those problems in production, he'll be able to talk about impact and what we should have done differently in the design."

  4. Allow enough time ahead of the meeting to allow the project manager and others to gather or compile information for reference. For example, during the first part of the meeting, the team reviews the original planned major milestone dates vs. the dates those milestones were actually achieved. That information should be brought to the meeting rather than creating it from memory on the spot.

  5. Send out the agenda, with appropriate statements about the importance of attendance by all invitees and expectations about 'tone' and spirit of the meeting. (Specifically, lessons learned meetings must be objective and professional - no "blame games" allowed.)

Note: This is a companion file to our Lessons Learned Meeting Report template, which talks in more detail about the conduct of the Lessons Learned meeting from this agenda, and the format of the resulting report.


The template requires a free Member account
Please log in to download the file. Don't have a log in? Register now, it's fast and free!
Log in to download this file

Username:  
Password:  





Related Templates
Agile Technique Brief – Retrospectives 
An agile approach to tracking and incorporating lessons learned during a project.

Lessons Learned Survey
A survey that can be sent to team members during or after a project, to solicit their feedback on how the project was conducted.

Lessons Learned Meeting Report 
Detailed instructions for running a Lessons Learned meeting, and a sample report.

Problem-Solving Tools and Techniques
Six different problem-solving tools help you do everything from determining root causes to assessing possible solutions, and outline a basic problem-solving strategy so you can be sure you've covered all the bases.





©Copyright 2000-2014 Emprend, Inc. All Rights Reserved.
About us   Site Map   View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy